LSCP must run as a started task or a started job. To run it as a started task, copy the procedure JCL to a JES PROCLIB data set. If you prefer to run it as a started job, copy the started job JCL to a data set in the IEFJOBS DD concatenation defined in your system Master JCL. A started job can call a procedure that resides in a non-JES private PROCLIB data set.
The following sample started task procedure JCL is provided in the SQDATA PROCLIB data set as member LSCP.
//*-------------------------------------------------------------------
//* Sample started task proc for LogStream Connection Pooler
//*
//* This proc may be called from started job JCL member SQDALSCP.
//*
//* The STEPLIB library must be APF-authorized.
//*-------------------------------------------------------------------
//LSCP PROC REG=100M,TYPE=,LLIB=SQDATA.V400.LOADLIB
//LSCP EXEC PGM=SQDALSCP,REGION=®,TIME=NOLIMIT,
// PARM='TYPE=&TYPE'
//STEPLIB DD DISP=SHR,DSN=&LLIB
//SYSPRINT DD SYSOUT=*
//SQDLOG DD SYSOUT=*The following sample started job JCL is provided in the SQDATA PROCLIB data set as member SQDALSCP.
//SQDALSCP JOB MSGLEVEL=(1,1),MSGCLASS=K
//*-------------------------------------------------------------------
//* Sample started job JCL for the LogStream Connection Pooler
//*
//* The LSCP proc may be in a JES or private PROCLIB. If using a
//* JES PROCLIB, delete the JCLLIB statement.
//*-------------------------------------------------------------------
//*
//PROC JCLLIB ORDER=(SQDATA.V400.PROCLIB)
//JESDS OUTPUT JESDS=ALL,OUTDISP=(WRITE,WRITE)
//*
//LSCP EXEC LSCP,LLIB=SQDATA.V400.LOADLIB