APAR status
INTRAN
Error description
This INFO APAR is extracted from the ITSC Redbook: SG24-4529-00. (MVS/ESA SP 5.2.2 OpenEdition MVS Installation and Customization Starter Kit -- December 1995). It also applies to OpenEdition Installation and Customization tasks in OS390 Release 1 and Release 2. The text is too long to fit in one APAR, so it is continued in a subsequent APAR, II10198. ================================================================ C.0 Appendix C. Troubleshooting One of the most daunting problems facing someone who has just installed all the components that make up the OpenEdition MVS product set is what to do when something goes wrong. C.1 List of Problems Encountered The following list contains examples of problems we specifically encountered while producing this book. Errors during OMVS startup After installing FMIDs JBB5522, JBB55N2, HOM1130, and JOM13N0 to upgrade from MVS 5.2.0 to 5.2.2. When starting OMVS you may get this message: CSV003I REQUESTED MODULE BPXEV012 NOT FOUND This is followed by a U4093 RC3F4 abend of BPXPLPKA. In MVS/ESA V5.1 of OpenEdition MVS the initialization program was shipped in /etc/init. Now in MVS/ESA V5.2.2 it is shipped in /usr/sbin/init. If you are installing OpenEdition MVS on top of a MVS/ESA V5.1 system you need to go in and delete the /etc/init program by hand (using the ISHELL). The order of search for the shell when looking for the initialization program is /etc/init first then /usr/sbin/init. If you don't delete the old /etc/init program by hand, then it will be incorrectly executed. This procedure will be documented in the PSP bucket for MVS/ESA V5.2.2 in the near future. IEF403I OMVS - STARTED - TIME=08.41.04 BPXF013I FILE SYSTEM OMVS.ROOT.HFS 371 WAS SUCCESSFULLY MOUNTED. BPXF203I DOMAIN AF_UNIX WAS SUCCESSFULLY ACTIVATED. BPXF203I DOMAIN AF_INET WAS SUCCESSFULLY ACTIVATED. BPXI018I THE /ETC/INIT PROCESS ENDED IN ERROR, EXIT STATUS 00000500 BPXI004I OMVS INITIALIZATION COMPLETE The ETC/INIT error above is caused by not having files, init.options and rc in the /etc directory. Copy /samples/init.options to /etc/init.options and copy /samples/rc to /etc/rc. Stop and restart OMVS. Console errors connecting TCP/IP to OpenEdition MVS EZY2141E OpenEdition-TCP/IP Connection error for TCPIP -BPX1SOC , FFFFFFFF,0000045A,112B0000 There are no TCP/IP definitions in the BPXPRMxx member of parmlib. See "Setting Up a Simple TCP/IP Environment" in topic 7.1.1 and "Setting Up the Multiple Transport Driver Support" in topic 7.1.2. EDC5112I Resource temporarily unavailable. EZY2141E OpenEdition-TCP/IP Connection error for TCPIPMVS -BPX1IOC , FFFFFFFF,0000009E,12B2005A EZY2140I OpenEdition-TCP/IP connection established for TCPIPOE BPXF206I ROUTING INFORMATION FOR TRANSPORT DRIVER TCPIPOE HAS BEEN INITIALIZED OR UPDATED. There are two transport providers running (TCPIPMVS and TCPIPOE) but only one is defined in the BPXPRMxx member of SYS1.PARMLIB. Only TCPIPOE can be used for OpenEdition MVS purposes. TCPIPMVS can be used for traditional MVS purposes. See Figure 176 in topic 7.1.2. Note: TCPIPMVS in message EZY2141E is the RACF user ID not the procedure name. EZY2141E OpenEdition-TCP/IP Connection error for STC -BPX1IOC , FFFFFFFF,0000009E,12B2005A Reasons for this message: - The associated RACF user ID for a TCP/IP started task has no OMVS segment. - The TCP/IP started task is not defined as SUBFILESYSTEM in the SYS1.PARMLIB BPXPRMxx member. - The associated RACF user ID for a TCP/IP started task is not the same as is defined in the SUBFILESYSTEM in the SYS1.PARMLIB BPXPRMxx member. Note: STC in message EZY2141E is the RACF user ID that the TCP/IP started task is associated with, not the procedure name. ISPF message after calling the ISHELL program Errno=9Dx A MVS environmental or internal error has occurred; Reason=0F04013D The process is not known to current kernel instance. Press Enter to continue. OMVS has probably been restarted during your TSO session. You have to log off and log on again. TSO message after issuing the OMVS command NOTE: The setting of your TSO PROFILE MSGIG will allow the Message Numbers to be displayed to enhance Problem Determination. If NOMSGID is set, the FSUMnnnI message numbers will be omitted from the messages below. FSUM2085I No session was started. OpenMVS was stopped and has been restarted. FSUM2086I Function = sigprocmask, return value = FFFFFFFF, return code 9D, reason code = 0F04013D *** OMVS has probably been restarted during your TSO session. You have to log off and log on again. Console message during APPC startup *ATB052E LOGICAL UNIT APPCOMVS FOR TRANSACTION SCHEDULER ASCH NOT ACTIVATED IN THE APPC CONFIGURATION. REASON CODE = 5A. There is no VTAM application defined and active for the LU, APPCOMVS. Nevertheless OMVS will work correctly, because it uses LU=OWN conversations under MVS/ESA 5.2.2. VTAM services are not used. Consider the message as informational only. It is working as designed. Console message during APPC/OMVS startup *BPXP003E OPENMVS INIT PROCESS CANNOT BE STARTED. 382 AN ERROR OCCURRED DURING APPC PROCESSING. APPC RETURN CODE = 10. VERIFY APPC AND APPC SCHEDULER ARE OPERATIVE, OR ENTER FORCE OMVS,ARM TO END PROCESSING. We had this problem intermittently when we tried to start OMVS before APPC and ASCH were all the way up. We had to stop and restart APPC and ASCH, then start OMVS to clear this up. Error using the TSO/E MOUNT command If the path name specified refers to the name of an already mounted file system the following message will be displayed on the screen: BPXF135E RETURN CODE 00000079, REASON CODE 055B005C. THE MOUNT FAILED FOR FILESYSTEM OMVS.SLEKKA.ROOT. *** The provided return code X'79' indicates that one of the parameters issued with the TSO/E MOUNT command is incorrect. The reason code is made up of 4 bytes. The high-order halfword is the reason code qualifier. The low-order halfword is the reason code description. If the reason code qualifier bytes are within the range of 0000 to X'20FF', then the error represented by the reason code is defined by OpenMVS. In other cases the returned reason code is not an OpenMVS reason code. The reason code qualifier of the captured error message is X'055B' and within the byte range specified above indicating an OpenEdition MVS error. The reason code itself X'005C' identifies a problem with the mount point named in the TSO/E MOUNT command. Finally, the return code X'79' defines the problem as trying to re-mount an HFS data set that is already mounted. For more information see Application Development Reference: Assembler Callable Services for OpenEdition MVS. Errors during OMVS session initialization Some errors could occur during initialization of the OpenEdition MVS shell by users that have not been defined to their security product correctly, for example: - No OpenEdition MVS definition. FSUM2057I No session was started. This TSO/E user ID does not have access to OpenMVS.+ FSUM2058I Function = sigprocmask, return value = FFFFFFFF, return code = 000009C, reason code = 0B0C00FB - Wrong shell program. FSUM2396 No session was started. The shell program could not be invoked Function = execve(), program name = 'noprogram', return value = -1, errno = 129 (X'00000081'), reason code = 057C006C, Message = 'EDC5129I No such file or directory.' Make sure the user has a valid shell program name defined in their OMVS segment in the PROGRAM field. - in the case of an ABENDEC6 RC C008, when reg3 contains the rc x'0507014D', the user has an invalid home directory. This instance occurred at V2R5 for a user attempting to ftp from option 6 in ISPF. - Wrong HOME directory. FSUM2078I No session was started. The home directory for this TSO/E userID does not exist or cannot be accessed.+ FSUM2079I Function = sigprocmask, return value = FFFFFFFF, return code 00000009, reason code = 0507014D List the user's OMVS segment information and check the OMVS HOME parameter. Check to make sure there is a valid mount point, pointing to a valid HFS data set. Information messages after INETD startup BPXF024I (OMVSKERN) Aug 23 14:29:22 inetd 524294 : login/tcp: socket: 742 EDC5112I Resource temporarily unavailable. BPXF024I (OMVSKERN) Aug 23 14:29:22 inetd 524294 : echo/tcp: socket: 743 EDC5112I Resource temporarily unavailable. BPXF024I (OMVSKERN) Aug 23 14:29:23 inetd 524294 : discard/tcp: 744 socket: EDC5112I Resource temporarily unavailable. BPXF024I (OMVSKERN) Aug 23 14:29:23 inetd 524294 : chargen/tcp: 745 socket: EDC5112I Resource temporarily unavailable. BPXF024I (OMVSKERN) Aug 23 14:29:23 inetd 524294 : daytime/tcp: 746 socket: EDC5112I Resource temporarily unavailable. BPXF024I (OMVSKERN) Aug 23 14:29:23 inetd 524294 : time/tcp: socket: 747 EDC5112I Resource temporarily unavailable. BPXF024I (OMVSKERN) Aug 23 14:29:23 inetd 524294 : echo/udp: socket: 748 EDC5112I Resource temporarily unavailable. BPXF024I (OMVSKERN) Aug 23 14:29:23 inetd 524294 : discard/udp: 749 socket: EDC5112I Resource temporarily unavailable. BPXF024I (OMVSKERN) Aug 23 14:29:24 inetd 524294 : chargen/udp: 750 socket: EDC5112I Resource temporarily unavailable. BPXF024I (OMVSKERN) Aug 23 14:29:24 inetd 524294 : daytime/udp: 751 socket: EDC5112I Resource temporarily unavailable. BPXF024I (OMVSKERN) Aug 23 14:29:24 inetd 524294 : time/udp: socket: 752 EDC5112I Resource temporarily unavailable. These messages are normal as long as the routing information between OMVS and the TCPIP transport providers has not been exchanged. You should get no further BPXF024I messages after the following message appears: EZY2140I OpenEdition-TCP/IP connection established for TCPIPOE BPXF206I ROUTING INFORMATION FOR TRANSPORT DRIVER TCPIPOE HAS BEEN INITIALIZED OR UPDATED. Problem with rlogin Compare your TCP/IP buffers with what is set in the examples shipped with this book. We had a problem with rlogin and it was caused by not having the TCP/IP TINYDATABUFFERPOOLSIZE value set to a large enough number. We set it to 384. Permission bit settings for new HFS data sets When a new HFS data set is allocated and a mount point directory is defined, the permission bits are set to 700 and the owner field contains the user ID that allocated the mount point directory. If this data set was allocated for a general OpenEdition MVS user, the owner field needs to be updated or the general OpenEdition MVS user will receive this message: ICH408I USER(USER1) GROUP(GID2) FID(......) INSUFFICIENT AUTHORITY TO OPEN ACCESS INTENT(-W-) ACCESS ALLOWED(GROUP R-X) Use the chown shell command to change the ownership of the mount point directory so this general user can access it. ============================================================ This INFO APAR is be continued in a subsequent INFO APAR -- II10198. - Reference manual SA22-7807-05 to determine the reason code and reason code description. -
Local fix
N/A
Problem summary
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II10197
Reported component name
PA LIB INFO ITE
Reported component ID
INFOPALIB
Reported release
001
Status
INTRAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
1997-01-30
Closed date
Last modified date
2007-10-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]
Document Information
Modified date:
01 October 2007