JCL needed to run IPCS in batch mode

Figure 1 shows the JCL needed to run IPCS in batch mode, and it shows how to invoke the BLSCSCAN CLIST to format a problem screening report for a stand-alone dump. The control information is saved in a dump directory data set that can be used for later formatting sessions in batch mode or at a terminal. This example assumes that you have an existing dump directory data set. For more information, see the z/OS MVS IPCS User's Guide.

Figure 1. JCL required to run IPCS in batch mode

//IPCSJOB  JOB 'acctinfo','PGMR output',MSGLEVEL=(1,1),
//          MSGCLASS=A,CLASS=J,NOTIFY=PGMR
//* ------------------------------------------------------
//*
//*   Input: dump in data set 'PGMR.DUMP1.DUMP'
//*   Output:
//*     - IPCS dump directory data set for the input dump
//*        (IPCSDDIR DD)
//*     - Formatted output (SYSTSPRT DD)
//*     - TSO/E messages (SYSTSPRT DD)
//*     All of the output will have message identifiers
//*     printed (with the PROFILE MSGID command in SYSTSIN)
//* ------------------------------------------------------
//IPCS     EXEC PGM=IKJEFT01,DYNAMNBR=20,REGION=1500K
//IPCSDDIR DD DSN=PGMR.DUMP.DIR,DISP=(OLD,KEEP)
//*
//SYSPROC  DD DSN=SYS1.SBLSCLI0,DISP=SHR
//SYSUDUMP DD SYSOUT=A
//SYSTSPRT DD SYSOUT=*
//SYSTSIN  DD *
PROFILE MSGID
IPCS NOPARM
SETDEF DSN('PGMR.DUMP1.DUMP') LIST NOCONFIRM
%BLSCSCAN
END
/*

Note: If you plan to use the IPCS output at a terminal after the batch job has completed, you may want to specify message and SYSOUT classes for held output rather than the MSGCLASS=A and SYSOUT=A on the DD statements in the example.