APAR status
Closed as canceled.
Error description
******************** JANUARY 10, 2002 ************************** RETAIN INFORMATION ITEMS WILL NO LONGER BE USED TO DOCUMENT COMMON USER ERROR INFORMATION. THE NEW PROCESS WILL RELAY THIS INFORMATION VIA THE SUPPORT PAGE WITHIN THE IMS HOME WEBSITE AT "HTTP://WWW.IBM.COM/IMS" CLICK ON THE "SUPPORT" KEYWORD IN THE LEFT MENU AREA. **************************************************************** THIS APAR IS BEING CREATED AS AN EXTENTION TO II02886 TO DOCUMENT COMMON ERRORS OR PROBLEMS ENCOUNTERED IN THE SYSTEMS AREA OF IMS. R102 R202 R304 R112 R213 R110 R314 R223 R120 R324 R273 R233 R130 R334 R152 R253 R150 R354 R162 R263 R160 R364 ITEM DESCRIPTION 1) IMSBATCH CPUTIME=0 HAS GIVES NO TIMING PAGE X 1 2) ABENDU0437 RC08 - PROBABLE USER ERROR PG. E1 3) ABEND80A ABEND878 CSA FILLING UP WHEN RUNNING PG. E3 ONLINE OR BATCH IMS. 4) ASSEMBLY ERRORS IN IMS USING DFP230 AS MACRO IHADCB PG. E4 HAS BEEN ELIMINATED AND DFP IS NOW USING THE DCBD MACRO. 5) MSGDFS2503W IS TRUNCATED ON JES2 JOB LOG. PG. E4 6) RTT MUST NOW BE IN DFSESL DD CARD LIBRARY PG. E5 7) MSGGIM44402 MSGGIM4441 MSGGIM4341 MSGGIM43401W OR PG. E5 MSGGIM4402W RECEIVED DURING THE APPLY OF IMS PTF'S. 8) ABENDU0688 RECEIVED UPON MPP STARTUP. PG. E8 9) ABEND0C4 DFSPCC20 OR ABEND90A DFSRRC40 PG. E9 10) ABEND0C4 DFSIMBE0 ATTEMPTING TO ENQUEUE AN SMB PG. E9 11) ABEND0C4 DFSMODU0 AFTER LABEL VSUBPOOL, X'1A06' PG. E11 12) ABEND019 RC0 DFSXBAT0 IF MVS DOWNLEVEL PG. E12 13) MSGIEW0234 FOR SYMBOL DFSCMS00 PG. E13 14) IMS ++HOLD GEN REQUIREMENTS PG. E14 15) ABEND106 RUNNING VS COBOL APPLICATION PROGRAMS PG. E15 16) PAPLRETC CONTAINS RC4C (HEX) RC76 (DECIMAL). PG. E16 17) DYNAMIC ALLOCATION AND IMSMON DATASET ON DASD PG. E17 18) ABENDU0016 DFSIINV0, MSGDFS1999I PG. E18 19) MSGIEF355A INITIATOR TERMINATED, NONREUSABLE PG. E18 20) ABEND0C4 DFSPCC30 OR DFSPCC20 - PL1 APPLICATION PG. E19 21) WAIT FROM IGX00024 PG. E21 22) WAIT IN ANY MODULE DURING XRF SHUTDOWN WITH THE ACTIVE AND ALTERNATE ON DIFFERENT PROCESSORS PG. E24 23) CMDASSIGN CMDASS TRAN TO CLASS STOPS WFI BMP PG. E26 24) DFSIXC01 RECEIVES RC12 FOR ALTLIB PG. E27 25) ABENDU0684 MSGDFS686W R310 RC503 RC51E R220 RC308 PG. E28 26) MSGDFS3421X ABENDU3421 RCTE FPSAMP1 PG. E29 27) Migration Guide GG243345-6 additional info XX) FUTURE UPDATES WILL BE MADE WITHIN THE IBM SUPPORT WEBSITE AT "WWW.IBM.COM/IMS". THE SUPPORT OPTION IS ON THE LEFT MENU. (January 10, 2002)
Local fix
1) THE IMSBATCH PROC HAS A PARM OF CPUTIME WHICH DEFAULTS TO 0 IF NOTHING IS SPECIFIED. THIS PARM SETTING WILL CAUSE IMS TO PUT A DUMMY VALUE IN THE TYPE07 LOG RECORD WHEN THE REGION TERMINATES. THE VALUE HAS NO RELATIONSHIP TO THE ACTUAL RUN TIME. THIS VALUE SETTING FOR CPUTIME IMPLIES THAT IMS DOES NOT DO ANY TIME CHECKING. ****************************************************************
Problem summary
2) ABENDU0437 RC08 "USER IS NOT AUTHORIZED TO USE THE SPECIFIED AGN" MSGDFS2854A RC08. THIS PROBLEM IS USUALLY CAUSED AS A RESULT OF THE RESOURCE ACCESS SECURITY USER EXIT, DFSISIS0, NOT BEING ALTERED TO CONTAIN ACTUAL USER SECURITY CODE. THE SAMPLE EXIT ROUTINE SHIPPED WITH IMS AUTOMATICALLY PLACES RC08 INTO REG15 TO INFORM THE USER THAT SECURITY HAS NOT BEEN ADDED. THE USER SHOULD SIMPLY LINK THEIR MODULE IN PLACE OF THE ONE SHIPPED WITH IMS. SCDISIS0 CONTAINS THE ADDRESS OF THIS USER EXIT ROUTINE, DFSISIS0. THE MODULE CAN BE EXAMINED IN STORAGE AFTER CREATING A CONSOLE DUMP OF THE CONTROL REGION TO DETERMINE WHETHER OR NOT THE EXIT HAS BEEN REPLACED WITH USER CODE. OFFSET X'18' WILL CONTAIN X'41F00008' (LA R15,8) IF THE ORIGINAL EXIT HAS NOT BEEN REPLACED. THIS, OF COURSE, WILL LEAD TO THE ABENDU0437. THE IMS GEN SECURITY MACRO USES THE TYPE=NOAGN PARAMETER TO CONTROL WHETHER OR NOT DFSISIS0 IS TO GAIN CONTROL. DFSISIS0 CAN ALSO BE PREVENTED FROM ACQUIRING CONTROL VIA THE ISIS=0 PARAMETER ON THE IMS STARTUP PROC. THIS WILL OVERRIDE THE GEN SPECIFICATION. =======================================MADDIX================= 3) ABEND878 OR ABEND80A, CSA FILLING UP CAN BE CAUSED BY NOT LINKING THE IMS RESOURCE CLEANUP MODULE, DFSMRCL0, INTO LPA OR NOT ZAPPING THE NAME DFSMRCL0 INTO CSECT IEAVTRML OF MODULE IGC0001C IN SYS1.LPALIB AS DEFINED IN THE IMS INSTALLATION PROCEDURES. A DEFINITE INDICATOR AS TO WHETHER OR NOT DFSMRCL0 IS SET UP PROPERLY IS TO NOTE WHETHER MSGDFS0627I OR MSGDFS0627W IS RECEIVED AT IMS TERMINATION TIME. IF THE MESSAGE IS NOT RECEIVED, THEN DFSMRCL0 IS NOT GAINING CONTROL AND THE RESOURCE CLEANUP ROUTINE SHOULD BE INSTALLED PROPERLY. ABENDC03 MAY ALSO BE RECEIVED ON SUBSEQUENT JOB STEPS IF DFSMRCL0 IS NOT PROPERLY INSTALLED. =======================================================MADDIX= 4)ASSEMBLY ERRORS IN IMS MODULES AS DFS2230 HAS REMOVED MACRO IHADCB FROM THIS RELEASE AND REPLACED IT WITH THE DCBD MACRO. CURRENT ASSEMBLY ERROR IN MODULE DFSDBAU0. =============================================================== 5) MSGDFS2503W IS TRUNCATED MAKING IT IMPOSSIBLE TO SEE THE RETURN CODE FOR THE FAILURE. THIS PROBLEM IS ADDRESSED BY JES2 APAR OY25965 WHICH DISCUSSES TRUNCATED MESSAGES ON THE JES 2 JOBLOG. I THE CUSTOMER DOES NOT HAVE THE APAR ON BUT WISHES TO SEE THE RC FOR DEBUGGING PURPOSES, THE MESSAGE DOES APPEAR IN ITS ENTIRETY ON THE SYSTEM CONSOLE. ======================================== MADDIX =============== 6) THE RTT USED WITH IMS/DB2 CONNECTIONS MUST BE PLACED IN THE LIBRARY DEFINED BY THE DFSESL DD CARD. APAR PL50237 NOW USES AN MVS LOAD FOR THE RTT RATHER THAN AN IMODULE LOAD TO PREVENT PROBLEMS WITH THE RTT NOT BEING FREED. ===============================================MADDIX========== 7) MSGGIM4441 MSGGIM44402 MSGGIM44401 MSGGIM44402W MSGGIM4341 MSGGIM43401W MAY BE RECEIVED WHILE APPLYING IMS MAINTENANCE. THE INFORMATION IN INFORMATIONAL APAR II00949 STILL HOLDS TRUE TODAY FOR ALL RELEASES OF IMS AND SHOULD BE REFERENCED. IN IMS310, CUSTOMER'S WHO ORDER THE IMSDB FEATURE AND GEN THEIR SYSTEM AS BATCH ONLY WILL RECEIVE A LARGE NUMBER OF THE ABOVE MENTIONED MESSAGES. THIS IS DUE TO NEW IMS 310 PACKAGING WHICH INCLUDES DBCTL MODULES. IF IMS IS GENNED AS A MINIMAL DBCTL SYSTEM, THEN MANY OF THESE MESSAGES CAN BE AVOIDED SINCE THE MODULES WILL BE INCLUDED IN RESLIB AS PART OF THE IMS GEN PROCESS. CICS 3.1 IS NOT REQUIRED TO PERFROM THIS GEN IF IMS IS EXECUTED AS A BATCH ONLY SYSTEM. THIS CIRCUMVENTION ONLY AFFECTS THE SIZE OF THE RESLIB CREATED AND THE AMOUNT OF TIME REQUIRED TO APPLY MAINTENANCE SINCE MORE MODULES WILL BE PRESENT IN THE RESLIB TO RECEIVE THE MAINTENANCE. TO UNDERSTAND WHETHER OR NOT THESE MESSAGES CAN BE IGNORED, THE PROCEDURE USED IN II00949 MAY BE USED, AND THE IMS GEN STAGE 2 OUTPUT CAN BE EXAMINED TO DETERMINE WHETHER OR NOT THE MODULE FLAGGED WAS INCLUDED IN THE RESLIB. IF IT WAS NOT LINKED AS PART OF THE STAGE 2 PROCESSING, THEN THAT INDICATES THAT THE MODULE IS NOT USED IN THE SYSTEM IN QUESTION, THUS, THE MESSAGE CAN BE IGNORED. NOTE: IF ONE INTENDS TO USE DBCTRL EVENTUALLY WITH CICS, IT IS BETTER TO GEN THE SYSTEM THAT WAY FROM THE START TO AVOID MOST OF THESE MESSAGES. ======================================== MADDIX ============= 8) ABENDU0688 CAN BE RECEIVED FOR AN MPP IF RESLIB IS SPECIFIED VIA JOBLIB FOR AN MPP. THE RESLIB SPECIFICATION CAN BE IGNORED FOR VARIOUS REASONS (SUCH AS SPECIFYING AN UNAUTHORIZED LIBRARY IN THE CONCATENATION), CAUSING AN UNINTENDED RESLIB TO BE FOUND FURTHER IN THE SEARCH SEQUENCE BY MVS WHEN LOADING MODULES, CONTROL BLOCKS, ETC. ======================================== MADDIX ============= 9) UPGRADING TO COBOL II (COBOL 2) FROM AN EARLIER VERSION, AN ABEND0C4 IN MODULE DFSPCC20, OR ABEND90A IN DFSRRC40 CAN OCCUR IF "STOP RUN" IS USED IN THE APPLICATION PROGRAM RATHER THAN "GOBACK" WHEN ATTEMPTING TO END THE PROGRAM. REG13 OF THE APPLICATION'S CALLER'S CALLER IS RETURNED TO ITS CALLER RATHER THAN REG13 FROM THE CALLER. THE METHOD OF RETURN IN THE APPLICATION WILL NEED TO BE CHANGED TO GOBACK. ======================================== MADDIX ============== 10) ABEND0C4 IN MODULE DFSIMBE0 ATTEMPTING TO ENQUEUE AN SMB ON THE TCT AFTER LABEL ENQ001. THIS COULD BE THE RESULT OF ATTEMPTING TO ENQUEUE AN SMB OF A GIVEN CLASS ONTO A TCT THAT HAS NOT BEEN DEFINED TO THE IMS SYSTEM. IF THE SMBCLASS FIELD IN THE SMB IN QUESTION (POINTED TO BY REG04) IS GREATER THAN THE NUMBER OF TCT'S DEFINED IN THE SYSTEM (SCD 2 BYTE FIELD: SCDTCTN), THEN THAT IS YOUR PROBLEM. THE MAXCLAS= PARM OF THE IMSCTRL MACRO SHOULD BE INCREASED TO ENCOMPASS THE TRANSACTION CLASS AS SPECIFIED IN THE TRANSACT MACRO FIELD, MSGTYPE, FOR THE TRAN IN QUESTION. OR, THE TRANSACTION CLASS SHOULD BE LOWERED TO MEET THE MAXCLAS LIMIT. THIS PROBLEM MAY HAVE MATERIALIZED BY RUNNING A GEN OF INSUFFICIENT MAGNITUDE TO CHANGE THE MAXCLAS PARM, BUT SUFFICIENT TO CHANGE THE TRANSACT MACRO, (SUCH AS MODBLKS GEN) =======================10/23/90==============MADDIX=========== 11). ABEND0C4 IN MODULE DFSMODU0 AFTER LABEL VSUBPOOL WHILE ATTEMPTING TO ACCESS THE SCD ON A TM INSTRUCTION AT SEQUENCE # 45780000. THIS CAN OCCUR DUE TO A RESIDUAL SSCVT ENTRY LEFT BEHIND AS A RESULT OF AN UNSUCCESSFUL IMS CLEANUP ATTEMPT. ONE COMMON CAUSE OF THE IMS CLEANUP FAILURE IS THAT DFSMRCL0 WAS NOT ZAPPED INTO IEAVTRML CSECT OF IGC0001C IN SYS1.LPALIB, AS WELL AS, NOT INCLUDING DFSMRCL0 IN LPALIB. =============================10/23/90=========MADDIX========== 12) IF THE CUSTOMER TRIES TO RUN IMS310 WITHOUT HAVING THE MVS APAR OY19751 ON, HE CAN RECEIVE AN ABEND019 RC0 IF A CSRCESRV SERVICE=QUERY REQUEST IS MADE TO MVS. THE CSRCESRV MACRO IS INTRODUCED IN THIS SPE AND OY19751 MUST BE ON FOR MVS TO SUPPORT IMS310. =============================10/30/90=======GRADY============= 13). "MSGIEW0234 LENGTH OF INPUT LOAD MODULE IN CONTROL DATA IS ZERO. CESD SYMBOL : DFSCMS00" RECEIVED DURING IMS INSTALL AT LINK OF DFSZZZ99. THIS IS DUE TO APAR OY27838 BEING APPLIED TO IEBCOPY. OY31883 WILL CORRECT THE PROBLEM OR ADVANCING TO DFP 330. "IEBCOPY COPYMOD" WILL ALSO NEED TO BE RUN AGAINST THE ORIGINAL DISTRIBUTION LIBRARY (IMSVS.LOAD) THAT LOAD MODULE DFSZZZ99 CAME FROM. THIS WILL CORRECT THE INVALID LENGTH INDICATOR CURRENTLY BEING USED. *UPDATE* THE MODULE THAT HAS TO BE SELECTED IN THE SELECT STATEMENT OF THE COPYMOD IS DFSZZZ99. THIS IS THE LOAD MODULE THAT INCLUDES DFSCMS00. USE IEBCOPY COPYMOD TO COPY DFSZZZ99 TO AN INTERMEDIATE DATASET, THEN COPY THE NEW DFSZZZ99 BACK TO IMSVS.LOAD. THE LINK STEP THAT FAILED CAN THEN BE RE-SUBMITTED. THE PROBLEM CAN BE CIRCUMENTED WITH A DOWN LEVEL LINKAGE EDITOR ============================= 04/22/92 =====MADDIX============= 14) FOR IMS DB ONLY SYSTEMS ONLY A BATCH SYSGEN MAY BE DONE. AFTER APPLYING & ACCEPTING OR ACCEPTING WITH BYPASS APPLY CHECK PTFS THAT INCLUDE ++HOLD STATEMENTS REQUIRING "ALL" GENS TO BE PERFORMED, THEN A "BATCH" GEN SHOULD BE DONE IN ITS PLACE. OTHER GEN TYPES SPECIFIED IN THE ++HOLD STATEMENTS (IE. ONLINE, CLTBLKS, NUCLEUS, MODBLKS) CAN BE IGNORED SINCE THOSE GEN TYPES ONLY AFFECT DC SYSTEMS. ===================================== MADDIX 11/23/90 ======== 15) ABEND106 CAN OCCUR IN IMS IF A USER IS RUNNING A NONPRELOADED COBOL PROGRAM, AND ONE OF THE PROGRAMS IN THE RUN IS COMPILED WITH THE RESIDENT AND NOENDJOB OPTIONS. THE LOW ORDER BIT WILL BE OFF (BIT 7) IN THE FIRST BYTE OF THE ILBOCOM BLOCK (OFFSET +X'00') IF ONE OF THE PROGRAMS FOR THE RUN UNIT WAS COMPILED WITH THE NOENDJOB OPTION. ILBOCOM CAN BE FOUND BY LOCATING ITS CDE IN THE ABEND106 DUMP. THIS IS TRUE FOR VS COBOL ===================================== KATRINA ================== 16) PAPLRETC CONTAINS RC4C (HEX) RC76 (DECIMAL). THIS RETURN CODE IS NOT DOCUMENTED IN THE IMS MESSAGES AND CODES MANUAL, NOR IN THE IMS CUSTOMIZATION GUIDE: DATABASE. THIS RETURN CODE IS USED TO INDICATE THAT THE LOAD REQUEST FOR DFSPZPXX HAS FAILED. THE SUFFIX VALUE MAY BE INCORRECT IN THE PAPL PASSED TO MODULE DFSPRRC0 FROM THE CCTL (CICS) SYSTEM AT PAPL OFFSET X'B9'. READER'S COMMENT FORM SUBMITTED TO DOCUMENT THE RC. ===================================== MADDIX =================== 17) ALTHOUGH THE UTILITES REFERENCE MANUAL WARNS THAT THE IMS MONITOR DATASET SHOULD BE ON TAPE IN ORDER FOR IT TO PARTICIPATE IN DYNAMIC ALLOCATION, IT IS POSSIBLE TO SPECIFY DASD IN THE PARAMETER LIST WHEN THE DFSDCMON MDA MEMBER IS BEING CREATED. THIS WILL CAUSE THE MONITOR DATASET TO BE ALLOCATED WITH A DISP OF 'NEW' EACH TIME THE MONITOR IS STARTED. THE DATASET THAT IS CATALOGED WILL BE EMPTY. THIS CAN ALSO CAUSE ALLOCATION FAILURE MESSAGES IF THERE ARE NO VOLUMES AVIALABLE TO ALLOCATE THE DATASET. IMS 6.1 APAR PQ04670 WILL ALLOW THE MONITOR DATASET TO BE DYNAMICALLY ALLOCATED ON DASD. ===================== BART/BUTTERWECK 7/1/97 ================ 18) ABENDU0016 DFSIINV0 MSGDFS1999I LOAD ERROR FOR VTAM TERMINAL CONTROL BLOCKS DFSCLV00 RC=0C ( RC0C ) THE DEFAULT REGION LIMIT SPECIFIED IN THE SMF EXIT IEFUSI IS 32MEG AND MAY BE EXHAUSTED WHEN RUNNING UNDER MVS/ESA IN AN IMS REGION. INCREASING THIS SIZE CAN RELIEVE THE PROBLEM BY ALLOWING MORE STORAGE FOR IMS. THE STORAGE FOR THE VTCBS IS GOTTEN FROM SP251 ABOVE THE 16M LINE. IMS CALCULATES THE SIZE OF THE HIOP POOL DURING SYSTEM DEFINITION BY ADDING UP THE OUTPUT BUFFER REQUIREMENTS FOR THE VTAM MSC AND FOR EACH DEFINED VTAM TERMINAL. THIS CALCULATED HIOP SIZE SATISFIES BOTH THE REQUIREMENT TO START THE ENTIRE VTAM NETWORK AT ONE TIME AND THE XRF TAKEOVER REQUIREMENTS. CHANGING THE HIOP STORAGE REQUIREMENT IS NOT RECOMMENDED IN R310. 19) "MSGIEF355A INITIATOR TERMINATED. RESTART INITIATORS" RECEIVED FOR IMS ASIDS ON TERMINATION. THIS IS DUE TO THE FACT THAT THE MVS SYSTEM WILL NOT REUSE ANY ASID WHICH HAS ESTABLISHED A PROGRAM CALL INTERFACE. SEE APAR OY26382 FOR ASID AVAILABILITY SUGGESTIONS USING THE RSVNONR PARAMETER. ================================== MADDIX ================= 20) ABEND0C4 IN MODULES DFSPCC30 OR DFSPCC20 UPON RETURN FROM THE LINK TO THE APPLICATION PROGRAM DUE TO INVALID REG01 OR REG03. IN DFSPCC30 THE FAILING INSTRUCTION IS THE "NI LIFLG3,255-LIDLI" INSTRUCTION, X'94BF3116' AFTER LABEL LINKAPPL. THIS OCCURS IN PL/I, PL1 APPLICATIONS ONLY. SEE PLI APARS PL33795 OR PL40024. ANOTHER PL1 ERROR THAT COULD RESULT IN THESE SYMPTOMS IS PL1 MODULE IBMBPIRA BEING DOWN LEVEL. THE EYECATCHER FOR THIS MODULE IS BPIR FOLLOWED BY THE RELEASE/AND OR COMPILE DATE FOR PRE VERSION 2 RELEASES. PL1 V2 RELEASE RESEMBLES IBMBPIR FOLLOWED BY THE VERSION/DATE. AN AMBLIST OF THE APPLICATION MODULE WILL PROVIDE THIS INFORMATION. SCAN FOR THE EYECATCHER 'BPIR'. ================================== MADDIX =================== 21) IMS HANGS DUE TO WAIT IN HSM MODULE IGX00024. THIS CAN OCCUR IN THE DYS OR DYA TCB IF AN IMS DATABASE DATASET IS MANANGED BY HSM, AND HSM HITS A SNAG IN ITS ATTEMPT TO RECALL THE DATASET. ONE IMS SAVE AREA FLOW THAT CAN BE SEEN IS DFSSMIC0 DFSSMSC1 DFSDBLM0 DFSDBAU0 DFSGDSNM DFSMDA10 DFSISERW. THE BOTTOM LINE IS THAT THE DYNAMIC ALLOCATION TCB CAN BE SEEN WAITING FROM MODULE IGX00024. IT IS CONSIDERED NORMAL FOR HSM TO OCCASIONALLY BE DELAYED IN ITS EFFORTS TO RECALL A DATASET. WHEN THIS OCCURS, ALL OF IMS CAN BECOME HUNG OR SEVERLY SLOWED DUE TO THE BLOCK MOVER LATCH (BML) BEING HELD WHILE THE RECALL IS PERFORMED. THEREFORE, IT IS NOT RECOMMENDED THAT THESE DATASETS BE ARCHIVED BY HSM. THIS CAN BE ACHIEVED AS FOLLOWS: - IF SMS MANAGED, USE THE APPROPRIATE SMS MANAGMENT CLASS WHICH WILL PREVENT THE MIGRATION. - USE THE "SET MIG" COMMAND TO CONTROL THE MIGRATION INTERVAL. - USE THE HSM USER EXITS DESIGNED FOR THE PURPOSE OF SPECIAL HANDLING OF SPECIFIC DATASETS. THE HSM MANUAL/AND OR OSS'S SHOULD HAVE INFORMATION REGARDING THE DETAILS OF THE PROCEDURES. TO FIND THE DATASET NAME BEING RETRIEVED, USE REG01 FROM THE RB FOLLOWING THE RB CONTAINING WLIC 00020063. IT WILL POINT TO THE DYNAMIC ALLOCATION PARAMETER LIST AND WILL CONTAIN THE DATASET NAME. =================================== MADDIX ===================== 22) A WAIT IN ANY MODULE DURING SHUTDOWN OF AN XRF SYSTEM MAY OCCUR IF THE ACTIVE AND THE ALTERNATE SUBSYSTEMS RESIDE ON DIFFERENT PROCESSORS, AND THERE IS ANOTHER DATASET ON THE SAME DEVICE AS THE OLDS AND WADS. THE SYSTEM ADMINISTRATION GUIDE STATES THAT "IF THE ACTIVE AND THE ALTERNATE SUBSYSTEMS RESIDE ON DIFFERENT PROCESSERS, A RESERVE IS ISSUED AGAINST THE OLDS AND WADS OF THE ACTIVE. IT IS RECOMMENDED THAT NO OTHER DATA SETS RESIDE ON THESE DEVICES BECAUSE THEY WOULD BE INACCESSIBLE ONCE THE RESERVE IS ISSUED. ACCESS TO THESE DATA SETS WHEN A TAKEOVER HAS BEGUN MIGHT ALSO HOLD UP THE TAKEOVER." THIS INFORMATION IS FOUND IS CHAPTER 12 OF THE RELEASE 2.2 MANUAL AND CHAPTER 15 OF THE RELEASE 3.1 MANUAL UNDERR THE SECTION ENTITLED "PHASES OF THE IMS COMPLEX" SUBHEADING "THE TAKEOVER PHASE". ============================= KATRINA ========================== 23) A BMP WHICH IS PROCESSING A WFI TRANSACTION IS PUT ON SUBQ6 WHEN THERE ARE NO MORE MESSAGES FOR IT TO PROCESS. IN THIS CASE, ONE OF THE LAST THINGS THE APPLICATION RUNNING IN THE BMP DID WAS TO ASSIGN THE TRAN THAT IT WAS PROCESSING TO A NEW CLASS. IN ORDER FOR THE CMDASSIGN TO TAKE EFFECT AS QUICKLY AS POSSIBLE, DFSICL70 WILL SCAN ALL ACTIVE PSTS TO FIND ANY THAT ARE SCHEDULED AGAINST THE SMB SPECIFIED BY THE ASSIGN TRANS CLASS COMMAND. IF THE PST IS WAITING ON SUBQ6, THE PST IS POSTED ' CCM', DEQUEUED AND A DETERMINATION IS MADE WHETHER OR NOT THE PST IS STILL ELIGIBLE TO WAIT ON SUBQ6. IN THE CASE OF THE BMP, IT WILL NO LONGER BE ELIGIBLE TO WAIT, AND STATUSQC WILL BE PASSED TO THE APPLICATION, AND THE BMP WILL TERMINATE. =====================4/10/91==== COMPTON ======================= 24) WHEN EXECUTING CLIST DFSIXC01 FOR INSTALL IVP, RC12 IS RECEIVED FOR THE ALTLIB FUNCTION. THIS IS DUE TO RUNNING WITH AN INVALID LEVEL OF TSO. THE FMID SHOULD BE HTE21D2 NOT HTE21C2. ====================================== MADDIX 04/11/91 ======== ABENDU0684 AND MSGDFS686W ARE OFTEN RECEIVED AFTER INSTALLING A NEW RELEASE OF THE MVS OPERATING SYSTEM. THIS IS USUALLY CAUSED BY THE OMISSION OF THE LINKEDIT OF THE IMS RESOURCE CLEANUP MODULE, DFSMRCL0, INTO LPALIB. IF MSGDFS627I WAS NOT RECEIVED ON THE SUBSEQUENT ATTEMPTS TO BRING IMS DOWN, THEN YOU CAN BE SURE THAT THE LINKEDIT AND ZAP WAS NOT PERFORMED PROPERLY AS DESCRIBED IN THE IMS INSTALLATION GUIDE. BE SURE THAT DFSMRCL0 IS ZAPPED FIRST IN THE LIST. ======================================= MADDIX 04/25/91 ======= 26) MSGDFS3421X RECEIVED FOR RCTE FPSAMP1. ABENDU3421 ALSO RECEIVED. THIS PROBLEM OCCURS BECAUSE THE RCTE'S WITHIN THE CBTE IPAGES WERE NOT PLACED IN ALPHABETICAL ORDER. THE RCTE'S SHOULD ALWAYS BE IN ALPHABETICAL ORDER. NORMALLY, THE STAGE 1 PORTION OF THE IMS SYSGEN WILL ORDER THE RCTE STATEMENTS PROPERLY. WE RECOMMEND THAT THE SORTING BE PERFORMED AT STAGE 1 TIME. THIS IS CONTROLED THROUGH THE NAMECHK PARM OF THE IMSCTRL MACRO. IF NAMECHK=NO,S2 WAS SPECIFIED, TRY NAMECHK=NO,S1. NAMECHK WILL DEFAULT TO S1 UNLESS OVERRIDDEN IN THE IMSCTRL MACRO NAMECHK PARM. (NOTE: DBFSBLK0 SCANS THE RCTE'S WITH A BINARY SEARCH BEFORE RETURNING A NOT FOUND RETURN CODE REG02 AT ABEND = X'00000008', RC08). =============================== MADDIX 05/20/91 ================
Problem conclusion
Temporary fix
Comments
INFORMATIONAL APAR
APAR Information
APAR number
II04204
Reported component name
PB LIB INFO ITE
Reported component ID
INFOPBLIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1990-01-26
Closed date
1990-02-16
Last modified date
2002-01-11
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":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"001"}]
Document Information
Modified date:
13 December 2020