Starting IXR and backup jobs but the IXR STC and the backup jobs hang with no error messages?
Article ID: 11920
Updated On:
Products
Issue/Introduction
How do we resolve the hang at startup of IXR? No error messages are being produced.
Starting IXR and backup jobs but the IXR STC and the backup jobs hang with no error messages?
Environment
Resolution
Usually messages will be issued in most cases. A hang with no IPC or JNL initialization messages being issued usually means that the JNL file has been opened properly and the IPC has been opened but the control record has yet to be read.
You would expect the following message to be issued:
ASMBR940 IPC INITIALIZATION FAILED, CODES(RSN=8,INFO=20,LOWINFO=24)
In the message manual you would look this up in the Appendix A to review the OPEN IPC error codes.
Since no messages was issued this means that the OPEN process for the IPC has not failed but has failed to load the control record from the IPC. IXR and backup jobs are waiting for the initialization to complete.
Cookbook to resolution:
Since the IPC is having a problem it would be best to cancel the tasks that are hanging.
1) REPRO the IPC out to a sequential file
sample JCL:
//STEP1 EXEC PGM=IDCAMS
//SYSUT1 DD DISP=SHR,DSN=your hlq.ASM2IPC
//SYSUT2 DD DSN=your hlq.ASM2IPC.SEQ,
// DISP=(NEW,CATLG,DELETE),
// DCB=(RECFM=VB,BLKSIZE=8196,LRECL=8192,DSORG=PS),
// SPACE=(CYL,(2,1)),VOL=SER=vvvvvv
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
REPRO INFILE(SYSUT1) OFILE(SYSUT2)
2) Delete the IPC and the JNL files and allocate new files
Sample JCL to allocate new IPC and JNL files and also initialize the files. The last step will repro your sequential file back into the new IPC
//STEP1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEF CL ( -
NAME(your hlq.ASM2IPC) -
UNIQUE FREESPACE(0 0) -
CISZ(4096) KEY(80 8) -
RECORDSIZE(512 4089) -
SHAREOPTIONS(3 3)) -
DATA ( -
NAME(your hlq.ASM2IPC.DATA) -
CYLINDERS(270 5) -
VOLUME(vvvvvv)) -
INDEX ( -
NAME(your hlq.ASM2IPC.INDEX) -
CYLINDERS(25 5) -
VOLUME(vvvvvv) -
CISZ(4096))
/*
//DEFINE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=(*)
//SYSIN DD *
DEFINE CLUSTER ( -
NAME(your hlq.ASM2JNL) -
CISZ(4096) -
RECORDSIZE(256 4089) -
REUSE -
SHAREOPTIONS(3 3) -
NONINDEXED -
) -
DATA ( -
NAME(your hlq.ASM2JNL.INDEX) -
CYLINDERS(25 5) -
VOLUME(vvvvvv) -
)
//*
//* ANALYZE AND INITIALIZE IPC/JNL
//*
//$$$$$$@ EXEC PGM=M2PCBRU
//STEPLIB DD DISP=SHR,DSN=your hlq.ASM242.CAILIB
//$OPTIONZ DD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//ISPMLIB DD DISP=SHR,DSN=your hlq.ASM242.CAIISPM
//ASM2IPC DD DISP=SHR,DSN=your hlq.ASM2IPC
//ASM2JNL DD DISP=SHR,DSN=your hlq.ASM2JNL
//SYSIN DD *
ANALYZE CATID(ASM2)
//STEP2 EXEC PGM=IDCAMS
//SYSUT1 DD DISP=SHR,DSN=your hlq.asm2ipc.seq,
//SYSUT2 DD DISP=SHR,DSN=your hlq.ASM2IPC
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
REPRO IFILE(SYSUT1) OFILE(SYSUT2) NOREPLACE ELIMIT=9999
3) If there is problems with the REPRO, such as a duplicate record condition, then this must be resolved before you can put the IPC back into production.
Additional Information
To resolve duplicate record conditions you must sort your IPC sequential file and remove the duplicate records. If you require assistance with this task you open an issue with CA Technical Support. The documentation required will be:
The REPRO job used to create the sequential file
Use TRSMAIN to compress the sequential file and send it in binary to the ASM2 support team. Attach the file to the issue.
Feedback
