Previous Topic: MVSNext Topic: Control Statement Format


VSE

Use JCL similar to the following example for CA Verify for CICS batch functions.

// JOB		RUN CA VERIFY BATCH FUNCTIONS
// DLBL		VERLIB,'CICS.VERIFY'
// EXTENT	,CICS01
// LIBDEF 	*,SEARCH=VERLIB.VERIFY
// DLBL   	IJSYSUC,'VSAM.USERCAT',,VSAM
// DLBL   	TCADSIN,'CICS.TCADS1',,VSAM
// DLBL		TCADSOU,'CICS.TCADS2',,VSAM
// ASSGN	SYSIPT,00C
// ASSGN	SYSLST,00E
// EXEC		PGM=TCABATCH,SIZE=512K[,PARM='LINECNT=nn']
DIRECTORY
/*
/&
TCABATCH

TCABATCH is the load module which performs batch functions. The size of the required region varies depending on the function, but 512 KB is usually enough. However, CA Verify for CICS may require additional storage when processing multiple terminal test streams.

You can specify a parameter to override the default number of lines per page:

PARM='LINECNT=nn'

where nn is a 2-digit number between 40 and 99. The default is 58.

Note: The batch functions can usually be run in 512 KB. For batch print using display format, allow 512 KB plus 8 KB per terminal.

LIBDEF

Required unless CA Verify for CICS is installed in a permanently assigned core image library.

TCADSIN

This DLBL statement defines the input data set for the Print, Copy, and Directory functions.

TCADSOU

This DLBL statement defines the output file for the Initialization, Format, Delete, and Copy functions.

SYSLST

Control statements, any error messages, and output from the Print and Directory List functions are written to this file.

SYSLST cannot be allocated to disk; tape or other sequential devices are acceptable. The file attributes are fixed unblocked 133-byte records with ASA carriage control.

SYSIPT

Defines the control statement input for batch functions. It can be allocated to disk, tape, or other sequential device. The record length can exceed 80 bytes.