APAR status
Closed as canceled.
Error description
This APAR is being taken to document common RODM non-defect problems. PROBLEM: Step 5, page 26 of the NetView Install Guide recommends placing any C or PL/I run-time library modules in LPALSTxx. C run-time ships a module called FREE. When the TSO FREE command was issued, it picked up the C/370 FREE module instead of the TSO FREE command processor that resided in LNKLST. This is because LPALST is searched before LNKLST. ANSWER: Remove the C run-time library modules from LPALSTxx. --------------------------------------------------------- PROBLEM: RODM RC/RSN 8/84 is not documented in V2R4 RODM Programming. This means that the user_id is already connected to RODM. ANSWER: Use another user_id to connect as RODM now only allows one connection per id at a time. --------------------------------------------------------- PROBLEM: ABENDS46D RC18 at RODM initialization. ANSWER: You must run with PLI V2R3 and C/370 V2R1 --------------------------------------------------------- PROBLEM: RC 8/127 when trying to run the loader job ( EKGLOTLM ) for userid EKGxx where xx is a numeric value that was not defined by the customer. Customer running ACF/2. ANSWER: For your RODM class definitions, type of EXTRACT and VERIFY must be defined because RODM checks the UAPI authorization. If Extract is not defined, then RODM creates this EKGxx userid and tries to VERIFY it. --------------------------------------------------------- PROBLEM: IEC161I 227-229 and IEC070I 203-204 at RODM startup. msgIEC161I msgIEC070I ANSWER: These messages are normal during RODM initialization. The IEC161I occurs because RODM is testing the existence of additional checkpoint datasets (EKGD003, EKGD004,etc). --------------------------------------------------------- PROBLEM: ABEND0C4 in DUIFCRTP at startup during structure load. Abend0c4 is in a DUIF* module in RODM address space. ANSWER: Problem is most likely due to an installation error. Be sure that post-linkedit jobs CNMSJ011 and CNMSJH05 were run and completed successfully. Ensure that those jobs were run using the v2r3 PL/I and v2r1 C/370 link-edit libraries. Lastly, make sure that the RODM procedure STEPLIB points to the v2r3 PL/I and v2r1 C/370 run-time libraries. --------------------------------------------- PROBLEM: DWO712E for DSIQTSK at task initialization in NetView 2.4 DWO712E is issued when an 8/128 is received from RACF or other security product. The RODM log will show the 8/128 which means password is invalid. Passwords are no longer required to connect to RODM, so this message is misleading. ANSWER: Define DSIQTSK to your security product and permit it as security level 6 as documented in Chapter 6 of the NetView Installation and Administration Guide. ----------------------------------------- PROBLEM: MSM Open base feature, using Command Tree/2 (CT/2) to add resource-specific commands for resources supported through MSM Open, fails with message DUI3763E (MSGDUI3763E) when the RODM resources have been built through the MSM Open Interface and display correctly on the GMF display. ANSWER: This can be caused by the use of a delimiter other than a separating period for GMFHS object names. All GMFHS object names require a '.' as a delimiter. ------------------------------------------- PROBLEM: I'm not using the RODM checkpoint function. How do I keep from allocating RODM checkpoint datasets? I sometimes get EKG1116I and/or EKG1117I messages which seem to be related to these datasets running out of storage. Can I disable the checkpoint function. ANSWER: Comment out the checkpoint datasets (dd=EKGMAST, EKGTRAN, EKGD001, EKGD002, EKGDnnn), in your RODM startup proc (EKGXRODM). You will then receive EKG1113I messages at RODM initialization stating that the checkpoint function is now disabled. PROBLEM: Experiencing unsuccessful LE/370 GETMAIN requests for below the line storage when running RODM. This may lead to an abend0C4 in a RODM recovery module, EKGSSxxx. ANSWER: See the discussion of the LE user option files, CEEUOPT and CEEDOPT, and the ALL31 parameter in II10227. Note: You may also need one or both of the LE APARs PQ00770 and PQ00696.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
NVINFO TPINFO
APAR Information
APAR number
II07892
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
1994-05-12
Closed date
1994-05-18
Last modified date
1998-04-06
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":"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"}}]
Document Information
Modified date:
14 December 2020