CA Dataquery requires that you name the system default JCL member for the online submission of a batch query $$DQJCL. No other default name is acceptable. The next sections provide sample $$DQJCL jobs. Use your Systems Programmer as the authority when creating user JCL members. The following $$DQJCL samples demonstrate the required statements for the $$DQJCL system default JCL.
Sample z/OS JCL
Following is a sample of a $$DQJCL job for z/OS.
//jobname See Preparing JCL for Batch CA Dataquery Utilities.
// EXEC PGM=DQBATCH
//STEPLIB See Preparing JCL for Batch CA Dataquery Utilities.
//SYSPRINT DD SYSOUT=* Print Output
//SYSUDUMP DD SYSOUT=*
//SNAPER DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//DQOUT DD ... Code according to your site standards if using EXPORT, or
//DQFIXD DD ... Code according to your site standards if using EXPORT
//SYSIN DD * Command input
/* DQ INPUT Œ
//
Œ
DQ INPUT is provided by the active member submitted by the user.
Sample z/VSE JCL
Following is a sample $$DQJCL member for z/VSE.
* $$ JOB ... See Preparing JCL for Batch CA Dataquery Utilities.
* $$ LST ...
// JOB name
// EXEC PROC=procname Whether you use PROCs or LIBDEFs, see Preparing JCL for Batch CA Dataquery Utilities.
// EXEC DQBATCH
// DLBL DQOUTD Code according to your site standards if using EXPORT, or
// TLBL DQOUTT Code according to your site standards if using EXPORT, or
// DLBL DQFIXD Code according to your site standards if using EXPORT, or
// TLBL DQFIXT Code according to your site standards if using EXPORT
/* DQ INPUT Œ
/*
/&
* $$ EOJ
Œ
DQ INPUT is provided by the active member submitted by the user.
|
Copyright © 2014 CA.
All rights reserved.
|
|