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. ****************** last updated lsk 06/08/2005 *************** The best way to get documention is using parmlib member IEADMCxx Dump parmlib support exists in OS/390 R2.5 and up where the DUMP commands can be pre-setup in parmlib members ( IEADMCxx ) similar to how the SLIP traps were used in the original MVS 5.1.0 timeframe. The DUMP parmlib avoids the use of SLIP IF (PER) which is limited to only one PER trap per system. IEADMCxx, where "xx" is the suffix you specify on the PARMLIB= operand of the DUMP command. example dump comm=( dumpname ) parmlib=xx example of what would go into IEADMCxx. This dump would get all the members of the group with XCF data and would be set on member aaa. DUMP COMM=(dump name here),DSPNAME=('aaa?IRLM'.*,'XCFAS'.*), JOBNAME=(XCFAS,aaa?IRLM,aaa?MSTR,aaa?DBM1,userjob), SDATA=(XESDATA,COUPLE,PSA,LSQA,LPA,GRSQ,SWA,RGN,CSA,SQA, SUM,TRT,ALLNUC),REMOTE=(SYSLIST=*('XCFAS','aaa?IRLM', 'aaa?MSTR','aaa?DBM1','bbbbMSTR','bbbbDBM1','bbbbIRLM'), DSPNAME=('aaa?IRLM'.*,'XCFAS'.*,'bbbbIRLM'.*),SDATA),end where aaaa = subsystem or member name of system where dump will be enabled. Note: If possible use the wild card '?' if the other member names are similar... otherwise add the bbbb where bbbb = subsystem or member name that does not match the generic naming conventions of aaa? ********************************************************** Please make sure you have a large enough dump dataset and use maxspace=2500 to get a complete dump. If you have more than one member on the same LPAR you might need a larger maxspace than 2500meg. Be careful not to include too many asids in joblist of slip. See II06335 for more information about preventing partial dumps. **************************************************************** The purpose of this APAR is to document how to obtain doc on Data sharing hang wait suspend issues involving DB2 or IMS and IRLM. If you have a DataSharing environment and you have a WAIT HANG LOOP SUSPEND that involves IRLM use this apar to obtain doc for IRLM release 2.1, DB2 r410 r510 R610 & IMS 4.1 and any other release of IMS 5.1 , 6.1 etc. See II06335 for additional information about DB2 hangs waits. See II08215 for Hang Wait issues involving DB2 DDF and DRDA. Get Status of all the members in the group by using the following commands: F irlmproc,STATUS,ALLD or F irlmproc,STATUS,ALLI see Command Reference Manual for more information. To obtain MVS console dumps of ALL members of the DataSharing group please use SLIP and the REMOTE keyword. The following are examples of MVS SLIP cmds to use to get useful doc: The SLIP is to be set on ALL members of the Data Sharing group. These slips are put in DISABLE so you can enable them when you need dumps. The MVS command to enable the dumps is SLIP MOD,ENABLE,ID=xxxx As soon as you enable the slip the dumps will be taken and they will disable themselves once the dumps are taken. SLIP SET,IF,N=(IEAVEDS0,00,FF),A=SVCD,disable,ID=xxxx, JOBLIST=(XCFAS,????IMS,????DLI,????IRLM), SDATA=(XESDATA,COUPLE,PSA,LSQA,LPA,GRSQ,SWA,RGN,CSA,SQA, SUM,TRT,ALLNUC),DSPNAME=('????IRLM'.*,'XCFAS'.*), REMOTE=(JOBLIST,SDATA,DSPNAME),END where ???? is the high level name of the members. example: member 1 member 2 member 3 DS2PIMS DS1PIMS DS3PIMS DS2PIRLM DS1PIRLM DS3PIRLM DS2PDLI DS1PDLI DS3PDLI HENCE ???? = ???P or DS?P or D??P etc. DSPNAME = data space name - using jobname of irlm and xcf WHERE xxxx is slip ID that you can use to enable the slip when the error occurs. Use the following SLIP command with DB2 and IRLM..... SLIP SET,IF,N=(IEAVEDS0,00,FF),A=SVCD,disable, JOBLIST=(XCFAS,????IRLM,????MSTR,????DBM1),ID=xxxx, SDATA=(XESDATA,COUPLE,PSA,LSQA,LPA,GRSQ,SWA,RGN,CSA,SQA, SUM,TRT,ALLNUC),DSPNAME=('????IRLM'.*,'XCFAS'.*), REMOTE=(JOBLIST,SDATA,DSPNAME),END where ???? is the high level name of the members. DSPNAME = data space name - using irlm & XCF jobname WHERE xxxx is your slip id that you can use to enable the slip when the error occurs. Note: reference the JOBLIST and ASIDLST parms of SLIP. The maximum amount of address spaces that 1 SYSPLEX member can dump in 1 instance is 15, with or without 'wildcards'. To limit the number of address spaces that are dumped, we suggest that the wildcards not be used instead dump the IRLM, MSTR and DBM1 address spaces as coded in the JOBLIST. For OS390 V2R5 and above see ow31938, new DUMP command function. **************************************************************** Using IRLM internal TRACES to capture documentation for problems 1) Using MVS TRACE command to turn TRACEs ON / OFF if you have DXRRL183 in LINKLIST: * If you turned the traces ON with the IRLMPROC, and want to turn then OFF with MVS, you must use the following sequence since MVS has no knowledge of the irlm trace STARTed STATUS: - TRACE CT,ON,COMP=irlmnm r nn,END - TRACE CT,OFF,COMP=irlmnm * To turn all subtypes ON: - TRACE CT,ON,COMP=irlmnm r nn,END trace ct,on,comp=pr21 *05 ITT006A SPECIFY OPERAND(S) FOR TRACE CT 5,end IEE600I REPLY TO 05 IS;END ITT038I ALL OF THE TRANSACTIONS REQUESTED VIA THE TRACE CT COMMAND WERE SUCCESSFULLY EXECUTED. * You can also manipulate individual subtypes except for INT and EXP: - TRACE CT,ON,COMP=irlmnm,SUB=(SLM) r nn,END - TRACE CT,OFF,COMP=irlmnm,SUB=(XIT) 2) Turning traces ON / OFF: * Using IRLMPROC Edit each IRLMPROC and change the trace keyword to 'TRACE=YES'. This enables all 6 subtypes of internal traces with default of 10 buffers 64k each. This means that the default ECSA required for each type is about 1/2meg so IRLM could use about 3meg total for tracing. These buffers are used in wrap-around mode and would be captured with a dump. The overhead is typically small, just few percent cpu. To INCREASE or DECREASE the number of trace buffers allowed, enter the MODIFY command: F prlm21,set,trace=60 DXR177I PR21001 THE VALUE FOR TRACES IS SET TO 60 The range for TRACE=xx with xx being 10 to 255 where each increase of 10 can require an additional 3meg of ECSA. When When the number is decreased, IRLM compression will slowly remove buffers down to the decreased amount with the lowest value of 10. If you are trying to capture doc for Level 2 ETR/PMR, always use the largest number of buffers that your current ECSA usage would safely allow. This allows the most data before the buffers start to wrap. * To verify the TRACE status, use : F irlmprocname,STATUS,TRACE F prlm21,status,trace DXR179I PR21001 TRACE USAGE TRACE BUFFER STORAGE IN USE: 64KB MAXIMUM NUMBER OF TRACE BUFFERS ALLOWED PER TRACE TYPE: 10 TRACE TYPE ACTIVE BUFFERS IN USE CTRACE WRITER ---------- ------ -------------- ------------- SLM Y 0 N XIT Y 0 N XCF Y 0 N DBM Y 0 N EXP Y 1 N INT Y 0 N DXR179I End of display ************************************************************ for issues with DXR167e with Notify_L slip to get a dump: SLIP SET,MSGID=DXR167E,DATA=(3R?+42,EQ,D3),ACTION=SVCD, DSPNAME=('xxxxIRLM'.*,'XCFAS'.*),ID=167e, JOBLIST=(XCFAS,xxxxIRLM,xxxxMSTR,xxxxDBM1), SDATA=(XESDATA,COUPLE,PSA,LSQA,LPA,GRSQ,SWA,RGN,CSA,SQA, SUM,TRT,ALLNUC),END with xxxx = jobname of IRLM, DB2mstr, DB2dbm1 **************************************************** FOR U2025 abends in DXRRL732 during startup check for DXR133I .... TIMEOUT DURING GLOBAL INITIALIZATION messages on all MEMBERS of the PLEX. This abendu2025 can indicate a timeout during global initialization caused by another member in the plex not responding or not communicating. The other member could be hung or looping or waiting. It is the real cause of the U2025 and to troubleshoot the issue the dump of the stuck member needs to be obtained. If customer does not know which member is causing the issue then get dumps of ALL MEMBERS in the GROUP or Check the DXR133I message for the system that shows WAITING.. EXAMPLE: DXR133I IRSF030 TIMEOUT DURING GLOBAL INITIALIZATION WAITING FOR IRSC ---------------------> <-------------- The system that is stuck is IRSC in this example and a dump of IRLM and the subsystem it is connected to - either DB2 or IMS asids needs to be obtained to get the necessary doc to solve the problem. ******************************************************** Note: To see the IRLMnm do F irlmproc,status,alld or Display Group detail and use the irlm subsystem name. ******************************************************** If you are in a loop you might want to increase the system trace and turn on branch trace. This should be done before the slip is enabled and while you are in the loop. TRACE ST,256k,BR=on Additional keywords: waiting waits hanging hung hangs suspend suspended loop looping Data share datasharing datashare SYSPLEX SYSPLEXDS IRLM = 569516401 r101 IMS = 569517611 r102 DB2 = 5740XYR00 r610 r710 Note: Disregard any 'LOCAL FIX' information noted in this apar.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
close for DB2INFO retention
APAR Information
APAR number
II10850
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
1997-10-09
Closed date
1997-10-16
Last modified date
2005-07-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":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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
06 July 2005