The application program can access the verification report after the CTJAPI SCAN call is completed. The following fields in the CTJAPI block are set:
The following example releases the 64 bit buffer:
*
FREE OUTPUT BUFFER
*
MVC JOBSTEP_TTOKEN,JAPIJMSGT GET TCB TOKEN
IARV64 REQUEST=DETACH, FREE MEMORY OBJECT X
COND=YES, CONDITIONAL REQUEST X
TTOKEN=JOBSTEP_TTOKEN, RELATE THE STOR TO TCB X
MATCH=SINGLE, X
MEMOBJSTART=JAPIJMSG@, AREA ADDRESS X
MF=(E,RV64PRMS) POINTER TO THE PARAMETERS AREA
Each message is 256 bytes long. The actual text starts in position 3 and is 132 bytes long.
The internal messages in the following table indicate the record types in the message buffer.
The calling program is responsible for releasing the message buffer. See Fig.JV.8.1 CTJAPI Macro Example - Verification in Examples.
Tab.JV.8.3 Internal messages
Message |
Description |
---|---|
CTJ100I |
Reserved for future use. |
CTJ101I |
Indicates an original JCL statement or comment in the verified member. |
CTJ102I |
Indicates a JCL statement or comment that was added to expand the JCL procedure in the verified member. The source of the addition is indicated by one of the following symbols, which starts the JCL text, as follows:
|
CTJ103I |
Indicates an IBM message that normally appears in the JESJCL or JESYSMSG when the JOB is submitted and executed. |
CTJ104I |
Indicates a SYSIN record. |
CTJ105I |
Indicates a "//SYSIN DD" statement, which Control-M JCL Verify generates when simulating JES2 or JES3. When the job is submitted, an asterisk is added as follows: //SYSIN DD * |
CTJ106I |
Reserved for future use. |
CTJ107I |
Reserved for future use. |
CTJ108I |
Reserved for future use. |
CTJ109I |
A null (//) JCL statement indicates the end of a job. |
Parent Topic |