Generated from a COBOL Copy File
|
Data Structure, MFJDXIT Generated from a COBOL Copy File |
|
|
| The SimoTime Home Page |
Introduction
This document was generated from a COBOL copy file using the SIMOTIME Record Layout utility program. The primary intent of the following table is to provide additional information about a file record layout using a COBOL Copy File as input. For example, the position of a field within a record is not easily determined from the COBOL Copy FIle. Also, the actual physical length for group items, packed fields, binary fields and tables is not explicitly defined. This information is calculated and provided by the SIMOTIME Record Layout utility program.
We have made a significant effort to ensure the documents and software technologies are correct and accurate. We reserve the right to make changes without notice at any time. The function delivered in this version is based upon the enhancement requests from a specific group of users. The intent is to provide changes as the need arises and in a timeframe that is dependent upon the availability of resources.
Copyright © 1987-2019
SimoTime Technologies and Services
All Rights Reserved
Record Structure
The physical length for the BINARY or COMP fields is calculated based on the format for an IBM Mainframe
| Level | Field/Redefines Name Directive for Binary is IBMCOMP |
Field Type | Relative Position |
Whole Numbers |
Decimal Positions |
Logical Size |
Physical Size |
Table Cell Size |
Table Minimum |
Table Maximum |
Redefine Depth |
| 01 | SIMOREC1-FORCE-01 | Group Item | 1 | 0 | 0 | 0 | 1212 | 0 | 0 | 0 | 0 |
| 3 | (TAG)-I-HEADER | Group Item | 1 | 0 | 0 | 0 | 30 | 0 | 0 | 0 | 0 |
| 5 | (TAG)-I-SIZE | Numeric/Signed BINARY |
1 | 8 | 0 | 8 | 4 | 0 | 0 | 0 | 0 |
| 5 | (TAG)-I-EVENT | Numeric/Signed BINARY |
5 | 8 | 0 | 8 | 4 | 0 | 0 | 0 | 0 |
| 5 | (TAG)-U-ACTION | Numeric/Signed BINARY |
9 | 8 | 0 | 8 | 4 | 0 | 0 | 0 | 0 |
| 5 | (TAG)-U-LOG-EVENT | Alphameric | 13 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 |
| 5 | PIC | Group Item | 14 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 5 | (TAG)-I-THIS-JOBNUM | Numeric/Unsign | 14 | 5 | 0 | 5 | 5 | 0 | 0 | 0 | 0 |
| 5 | (TAG)-I-THIS-JOBNAME | Alphameric | 19 | 0 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 5 | (TAG)-I-THIS-PROC-ID | Numeric/Unsign BINARY |
27 | 9 | 0 | 9 | 4 | 0 | 0 | 0 | 0 |
| 3 | (TAG)-I-DATA | Alphameric | 31 | 0 | 0 | 368 | 368 | 0 | 0 | 0 | 0 |
| 3 | REDEFINES | Group Item | 399 | 0 | 0 | 0 | 207 | 0 | 0 | 0 | 0 |
| 5 | (TAG)-I-DATA-JOB-READY | Group Item | 399 | 0 | 0 | 0 | 316 | 0 | 0 | 0 | 0 |
| 7 | PIC | Group Item | 399 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-PC-FNAME | Alphameric | 399 | 0 | 0 | 260 | 260 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-MVS-DSN | Alphameric | 659 | 0 | 0 | 54 | 54 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-SUBMIT-TYPE | Alphameric | 713 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-ANIMATE | Alphameric | 714 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 |
| 3 | REDEFINES | Group Item | 715 | 0 | 0 | 0 | 207 | 0 | 0 | 0 | 0 |
| 5 | (TAG)-I-DATA-UXIT-CHGD-JOBNAME | Group Item | 715 | 0 | 0 | 0 | 8 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-OLD-JOBNAME | Alphameric | 715 | 0 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 3 | REDEFINES | Group Item | 723 | 0 | 0 | 0 | 207 | 0 | 0 | 0 | 0 |
| 5 | (TAG)-U-DATA-JOB-STMT-INFO | Group Item | 723 | 0 | 0 | 0 | 279 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-JOBNAME | Alphameric | 723 | 0 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-TYPRUN | Numeric/Unsign BINARY |
731 | 4 | 0 | 4 | 2 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-MSGCLASS | Alphameric | 733 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-MSGLEVEL-1 | Numeric/Unsign | 734 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-MSGLEVEL-2 | Numeric/Unsign | 735 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-USERID | Alphameric | 736 | 0 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-PGMR-NAME | Alphameric | 744 | 0 | 0 | 20 | 20 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-JOBCLASS | Alphameric | 764 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-PRTY | Alphameric BINARY |
765 | 0 | 0 | 8 | 4 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-NOTIFY-NODE | Alphameric | 769 | 0 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-NOTIFY-USERID | Alphameric | 777 | 0 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-PASSWORD | Alphameric | 785 | 0 | 0 | 32 | 32 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-PASSWORD-NEW | Alphameric | 817 | 0 | 0 | 32 | 32 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-SECLABEL | Alphameric | 849 | 0 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-JOB-PERFORM | Numeric/Unsign BINARY |
857 | 4 | 0 | 4 | 2 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-ACCT-VALUE | Alphameric | 859 | 0 | 0 | 143 | 143 | 0 | 0 | 0 | 0 |
| 7 | PIC | Group Item | 1002 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 3 | REDEFINES | Group Item | 1002 | 0 | 0 | 0 | 207 | 0 | 0 | 0 | 0 |
| 5 | (TAG)-I-DATA-JOB-CONCL | Group Item | 1002 | 0 | 0 | 0 | 4 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-CONCL-RC | Numeric/Signed BINARY |
1002 | 8 | 0 | 8 | 4 | 0 | 0 | 0 | 0 |
| 3 | REDEFINES | Group Item | 1006 | 0 | 0 | 0 | 207 | 0 | 0 | 0 | 0 |
| 5 | (TAG)-I-DATA-JOB-STARTED | Group Item | 1006 | 0 | 0 | 0 | 80 | 0 | 0 | 0 | 0 |
| 7 | POINTER | Group Item | 1006 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 7 | POINTER | Group Item | 1006 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 7 | POINTER | Group Item | 1006 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-SYSTEM | Alphameric | 1006 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-SUBSYSTEM | Alphameric | 1007 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-JOBNAME | Alphameric | 1008 | 0 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-USERID | Alphameric | 1016 | 0 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-JOBSTEP | Alphameric | 1024 | 0 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-PROCSTEP | Alphameric | 1032 | 0 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-JOBNUM | Numeric/Unsign | 1040 | 5 | 0 | 5 | 5 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-STEPNUM | Numeric/Unsign | 1045 | 3 | 0 | 3 | 3 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-PROCSTEPNUM | Numeric/Unsign | 1048 | 3 | 0 | 3 | 3 | 0 | 0 | 0 | 0 |
| 7 | PIC | Group Item | 1051 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 7 | PIC | Group Item | 1051 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-MSGCLASS | Alphameric | 1051 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-MSGLEVEL1 | Alphameric | 1052 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-MSGLEVEL2 | Alphameric | 1053 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 |
| 7 | PIC | Group Item | 1054 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 7 | PIC | Group Item | 1054 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-JOB-START-DATE | Numeric/Unsign | 1054 | 8 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-JOB-START-TIME | Numeric/Unsign | 1062 | 8 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-STEP-START-DATE | Numeric/Unsign | 1070 | 8 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-I-STEP-START-TIME | Numeric/Unsign | 1078 | 8 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 5 | (TAG)-U-DATA-JOB-ENDED | Group Item | 1086 | 0 | 0 | 0 | 9 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-TERM-TYPE | Alphameric | 1086 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 |
| 7 | PIC | Group Item | 1087 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-TERM-RETURN-CODE | Numeric/Signed BINARY |
1087 | 8 | 0 | 8 | 4 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-TERM-REASON-CODE | Numeric/Signed BINARY |
1091 | 8 | 0 | 8 | 4 | 0 | 0 | 0 | 0 |
| 5 | (TAG)-I-DATA-STEP-READY | Group Item | 1095 | 0 | 0 | 0 | 118 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-PGM-NAME | Alphameric | 1095 | 0 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-PGM-ALIAS | Alphameric | 1103 | 0 | 0 | 8 | 8 | 0 | 0 | 0 | 0 |
| 7 | (TAG)-U-PGM-PARM | Group Item | 1111 | 0 | 0 | 0 | 102 | 0 | 0 | 0 | 0 |
| 9 | (TAG)-U-PGM-PARM-LEN | Numeric/Signed BINARY |
1111 | 4 | 0 | 4 | 2 | 0 | 0 | 0 | 0 |
| 9 | (TAG)-U-PGM-PARM-TXT | Alphameric | 1113 | 0 | 0 | 100 | 100 | 0 | 0 | 0 | 0 |
| Level | Field/Redefines Name Directive for Binary is IBMCOMP |
Field Type | Relative Position |
Whole Numbers |
Decimal Positions |
Logical Size |
Physical Size |
Table Cell Size |
Table Minimum |
Table Maximum |
Redefine Depth |
COBOL Copy File
The following shows the content of the COBOL Copy File that defines the fields within a record structure (or record layout).
*===============================================================
* Copyright (C) 1997-2006 Micro Focus (IP) Limited. All rights
* reserved.
*===============================================================
*
* MFJDXIT - JCL User Exit Control Block
* Contains interface information and is passed as a parameter
* to the JCL user exit (MFJUXIT) which is invoked as
* call 'MFJUXIT' using JXIT
*
* Notes:
* 1. It should be included as follows (e.g.)
* 1 JXIT.
* COPY MFJDXIT REPLACING ==(tag)== BY ==JXIT==.
* 2. Fields beginning with JXIT-I- ( (tag)-I- ) are Input
* to the user exit and must not be modified
* e.g. JXIT-I-size
* 3. Fields beginning with JXIT-U- ( (tag)-U- ) are Input and
* Output. On entry to the user exit, they are set as
* appropriate and may be changed by the user exit to an
* acceptable value upon return.
* e.g. (tag)-U-PGM-alias
* 4. All data is ASCII(ANSI). Null values are those appropriate
* for the data type. i.e. blanks for character data,
* zeros for numeric and binary data
*
* --Date--- Who --What------------------------------------------
* 2002Mar04 DSA Initial version
* 2003Apr25 DSA Changes as a result of addition of support for
* Event-step-ready
* 2005Sep07 DSA Added new event event-job-concluded and
* event event-job-purged
* 2006Oct13 - Added Event-job-stmt-info and
* Event-uxit-chgd-jobname
*
*===============================================================
*===============================================================
* Header
*===============================================================
3 (tag)-I-header.
* Size of this block
5 (tag)-I-size pic s9(8) comp.
* Unless otherwise noted, all events occur for
* JCL, TSO, and TSO-in-batch (PGM=IKJEFTxx or IDAEFTxx)
* Event code of event. Ignore undefined event codes.
5 (tag)-I-event pic s9(8) comp.
* The following events occur for JCL and TSO-in-batch
* and represent execution of a JCL JOB stream
88 (tag)-I-event-job-ready value 1.
88 (tag)-I-event-job-stmt-info value 25. *> This
*> event is broadcast ONLY to the JCL user exit
88 (tag)-I-event-uxit-chgd-jobname value 26. *>
*> event is broadcast ONLY to the event manager
88 (tag)-I-event-job-concluded value 2.
88 (tag)-I-event-job-started value 3.
88 (tag)-I-event-job-purged value 4.
88 (tag)-I-event-job-ended value 5.
* The following events occur for an interactive TSO
* session only
88 (tag)-I-event-TSO-started value 6.
88 (tag)-I-event-TSO-ended value 7.
* The following events occur for JCL and TSO-in-batch
* and represnt execution of "EXEC PGM=" JCL stmt
88 (tag)-I-event-step-ready value 8.
88 (tag)-I-event-step-started value 9.
88 (tag)-I-event-step-ended value 10.
88 (tag)-I-event-step-bypassed value 11.
* The following events occur for TSO and TSO-in-batch
* (IKJEFT01) and
* ... represent execution of the TSO "CALL pgm" command
88 (tag)-I-event-CALL-ready value 12.
88 (tag)-I-event-CALL-started value 13.
88 (tag)-I-event-CALL-ended value 14.
* ... represent execution of the DSN subcommand
* "RUN PROG(pgm)"
88 (tag)-I-event-RUN-ready value 15.
88 (tag)-I-event-RUN-started value 16.
88 (tag)-I-event-RUN-ended value 17.
*
* Under MFE, all events, except Event-before-PGM-call and
* Event-after-PGM-call, occur in the parent process.
* These two events occur in the child process.
*
* Under ESJCL,
* - Event-job-ready, Event-uxit-chgd-jobname, and
* Event-job-purged events
* occur only in the Service Execution Process (SEP),
* not in the initiator SEP.
* - Event-job-concluded event occurs in the standard SEP
* only if the job is not intended for execution (i.e.
* it is TYPRUN=COPY or TYPRUN=SCAN) or it has JCL
* errors. Otherwise this event occurs in the initiator
* SEP.
* - All other events occur in the initiator SEP.
*
*
* The following events occur for all environments
* for execution of a program following all
* "...-started" events.
* ***Note*** that these events occur in the child process
* that executes the program. Any working storage used by
* the user exit will not be the same as that for
* other events which occur in the parent process.
* In the parent process, your user exit will not remember
* information prior to "event-before-PGM-call" or after
* "event-after-PGM-call". Since both of these events
* occur in the shild process, the user exit will be
* able to remember information between these two events.
88 (tag)-I-event-before-PGM-call value 18.
88 (tag)-I-event-after-PGM-call value 19.
* Event codes 25 thru 50 reserverd for JCL User exit
* Event codes 51 thru 99 reserverd for JES Monitor
* 88 (tag)-I-event-job-stmt-info value 25. See above
* 88 (tag)-I-event-uxit-chgd-jobname value 26. See above
*===============================================================
* Action codes for all events. Upon return from the user exit,
* action code indicates next course of action to be taken.
* Upon entry to the user exit, it is set to zero.
*===============================================================
5 (tag)-U-action pic s9(8) comp.
* The JCL engine should continue as if the exit were
* never invoked. Any modified data will be ignored.
88 (tag)-U-action-continue value 0.
* The JCL engine should not call the exit any more in
* this process for this job/TSO session
88 (tag)-U-action-shut-exit value 1.
*===============================================================
* Action codes for: event-job-ready
*===============================================================
* The JCL engine should use all modified
* fields except pc-fname
88 (tag)-U-action-MVS-dsn value 2.
* The JCL engine should use all modified
* fields except MVS-dsn
88 (tag)-U-action-pc-fname value 3.
* The JCL engine should flush the job
88 (tag)-U-action-flush value 4.
*===============================================================
* Action codes for: event-job-stmt-info
*===============================================================
* The JCL engine should use all modified
* job information (action-continue)
* See 88 (tag)-U-action-flush above
*===============================================================
* Action codes for: event-step-ready
* event-CALL-ready
* event-RUN-ready
*===============================================================
* The JCL engine should use all modified fields
88 (tag)-U-action-PGM-info value 5.
* The JCL engine should abend this step/program.
* The step/program will be abended with
* S822 (Region not available)
88 (tag)-U-action-abend value 6.
*===============================================================
* Action codes for: event-job-ended
* event-TSO-ended
* event-step-ended
* event-CALL-ended
* event-RUN-ended
*===============================================================
* The JCL engine should use all modified fields
88 (tag)-U-action-term-info value 7.
*===============================================================
* Action codes for: event-job-started
* event-TSO-started
* event-step-bypassed
* event-step-started
* event-CALL-started
* event-RUN-started
* event-before-PGM-call
* event-after-PGM-call
* - No Action codes defined other than 0
*===============================================================
5 (tag)-U-log-event pic x.
* The JCL engine should log all events (default)
88 (tag)-U-log-event-on value x'00'.
* The JCL engine should log only those events for which
* the exit requests a explicit action (non- 0 or 1)
88 (tag)-U-log-event-on-action value x'01'.
* The JCL engine not log any events unless
* requested to do so otherwise in the future
88 (tag)-U-log-event-off value x'02'.
* The JCL engine should log most events,
* currently all except
* - job-event-concluded
88 (tag)-U-log-event-on-min value x'03'.
5 pic x(2).
* Job number - may be 0 if not yet available
5 (tag)-I-this-jobnum pic 9(5).
* Job name - may be '????????' if not yet available
5 (tag)-I-this-jobname pic x(8).
* Process id
5 (tag)-I-this-proc-id pic 9(9) comp.
*===============================================================
* Event related data - varies by event
*===============================================================
3 (tag)-I-data pic x(368).
*===============================================================
* Data for: event-job-ready
*===============================================================
3 redefines (tag)-I-data.
5 (tag)-I-data-job-ready.
* reserved (used to be Job number). Use I-this-jobnum
7 pic 9(5).
* Fully qualified PC file name.
7 (tag)-U-pc-fname pic x(260).
* If available, MVS data set name (including member if
* a PDS) assoicated with pc-fname, otherwise blanks.
* e.g. MFIDSA.CNTL(MYJOB) (for a PDS member) or
* S0310.S070508.J01364.D00002.SYSUT2 (for PS)
7 (tag)-U-MVS-dsn pic x(54).
*
7 (tag)-I-submit-type pic x(1).
88 (tag)-I-submit-type-exec value 'E'.
88 (tag)-I-submit-type-scan value 'S'.
7 (tag)-I-animate pic x(1).
88 (tag)-I-animate-on value 'Y'.
88 (tag)-I-animate-off value 'N'.
*===============================================================
* Data for: event-uxit-chgd-jobname
*===============================================================
3 redefines (tag)-I-data.
5 (tag)-I-data-uxit-chgd-jobname.
7 (tag)-I-old-jobname pic x(8).
*> This was the jobname on the job card. it was changed
*> by the JCL user exit to -i-this-jobname (above).
*===============================================================
* Data for: event-job-stmt-info
*===============================================================
3 redefines (tag)-I-data.
5 (tag)-U-data-job-stmt-info.
7 (tag)-U-jobname pic x(8).
7 (tag)-U-typrun pic 9(4) comp.
88 (tag)-U-typrun-scan value 0.
88 (tag)-U-typrun-exec value 1.
88 (tag)-U-typrun-anim value 2.
88 (tag)-U-typrun-copy value 3.
88 (tag)-U-typrun-hold value 4.
7 (tag)-U-msgclass pic x(1).
7 (tag)-U-msglevel-1 pic 9(1).
7 (tag)-U-msglevel-2 pic 9(1).
7 (tag)-U-userid pic x(8).
7 (tag)-U-pgmr-name pic x(20).
7 (tag)-U-jobclass pic x(1).
7 (tag)-U-prty pic 9(4) comp. *> 0-15
7 (tag)-U-group pic x(8).
7 (tag)-U-notify-node pic x(8).
7 (tag)-U-notify-userid pic x(8).
7 (tag)-U-password pic x(32).
7 (tag)-U-password-new pic x(32).
7 (tag)-U-seclabel pic x(8).
7 (tag)-U-job-perform pic 9(4) comp. *> 1-999
7 (tag)-U-acct-len pic 9(4) comp.
7 (tag)-U-acct-value pic x(143).
7 pic x(81).
*===============================================================
* Data for: event-job-concluded
*===============================================================
3 redefines (tag)-I-data.
5 (tag)-I-data-job-concl.
* Job processing outcome
7 (tag)-I-concl-rc pic s9(8) comp.
88 (tag)-I-concl-rc-ended value 1.
88 (tag)-I-concl-rc-abended value 2.
88 (tag)-I-concl-rc-jcl-error value 3.
88 (tag)-I-concl-rc-scanned value 4.
88 (tag)-I-concl-rc-scan-failed value 5.
88 (tag)-I-concl-rc-flush-no-job value 6.
88 (tag)-I-concl-rc-flush-bad-job value 7.
88 (tag)-I-concl-rc-flush-uxit value 8.
88 (tag)-I-concl-rc-copied value 9.
88 (tag)-I-concl-rc-cancelled value 10.
88 (tag)-I-concl-rc-authfailed value 11.
*===============================================================
* Data for: event-job-flushed
* See event-job-ready.
* - Only the first field is relevant
*===============================================================
*===============================================================
* Data for: event-job-started
* event-TSO-started
* event-step-bypassed
* - Field names containing "step" are irrelevant for non-step
* related events
*===============================================================
3 redefines (tag)-I-data.
5 (tag)-I-data-job-started.
7 pointer.
7 pointer.
7 pointer.
*
* Active System and Subsystems combinations are:
* System Subsystem
* ----------------
* JCL JCL
* JCL TSO (IKJEFTxx)
* JCL IMS (DFSRC000)
* TSO TSO
* TSO IMS (CALL DFSRC000)
* IMS IMS
* CICS CICS
*
* Active system
7 (tag)-I-system pic x.
88 (tag)-I-system-JCL value x'00'.
88 (tag)-I-system-TSO value x'01'.
88 (tag)-I-system-ims value x'02'.
88 (tag)-I-system-cics value x'03'.
88 (tag)-I-system-null value x'04'.
* Active subsystem
7 (tag)-I-subsystem pic x.
88 (tag)-I-subsystem-JCL value x'00'.
88 (tag)-I-subsystem-TSO value x'01'.
88 (tag)-I-subsystem-ims value x'02'.
88 (tag)-I-subsystem-cics value x'03'.
88 (tag)-I-subsystem-null value x'04'.
7 (tag)-I-jobname pic x(8).
7 (tag)-I-userid pic x(8).
7 (tag)-I-jobstep pic x(8).
7 (tag)-I-procstep pic x(8).
7 (tag)-I-jobnum pic 9(5).
7 (tag)-I-stepnum pic 9(3).
7 (tag)-I-procstepnum pic 9(3).
7 pic x(1).
7 pic x(1).
7 (tag)-I-msgclass pic x(1).
7 (tag)-I-msglevel1 pic x(1).
7 (tag)-I-msglevel2 pic x(1).
7 pic x.
7 pic x(1).
* Dates in YYYYMMDD format, times in HHMMSShh
7 (tag)-I-job-start-date pic 9(8).
7 (tag)-I-job-start-time pic 9(8).
7 (tag)-I-step-start-date pic 9(8).
7 (tag)-I-step-start-time pic 9(8).
*===============================================================
* Data for: event-job-ended
* event-TSO-ended
* event-step-ended
* event-CALL-ended
* event-RUN-ended
* event-after-PGM-call
* See event-job-started
* - plus the following data
*===============================================================
5 (tag)-U-data-job-ended.
7 (tag)-U-term-type pic x.
88 (tag)-U-term-type-normal value x'00'.
88 (tag)-U-term-type-user-abend value x'01'.
88 (tag)-U-term-type-sys-abend value x'02'.
88 (tag)-U-term-type-RTS-err value x'03'.
88 (tag)-U-term-type-RU-err value x'04'.
88 (tag)-U-term-type-unknown value x'05'.
7 pic x(3).
7 (tag)-U-term-return-code pic s9(8) comp.
7 (tag)-U-term-reason-code pic s9(8) comp.
*===============================================================
* Data for: event-step-ready
* event-step-started
* event-CALL-ready
* event-CALL-started
* event-RUN-ready
* event-RUN-started
* event-before-PGM-call
* See event-job-started
* - Plus the following data
* - Field names containing "step" are relevant
*===============================================================
5 (tag)-I-data-step-ready.
7 (tag)-U-PGM-name pic x(8).
7 (tag)-U-PGM-alias pic x(8).
7 (tag)-U-PGM-parm.
9 (tag)-U-PGM-parm-len pic s9(4) comp.
9 (tag)-U-PGM-parm-txt pic x(100).
*= End of MFJDXIT ==============================================
Summary
This document was generated by the SIMOTIME Record Layout utility program. The primary intent is to provide additional information about a record structure based on the field definitions from a COBOL Copy File. This document may be used to assist as a tutorial for new programmers or as a quick reference for experienced programmers.
In the world of programming there are many ways to solve a problem. This document and the links to other documents are intended to provide a greater awareness of the Data Management and Application Processing alternatives.
The documentation and software were developed and tested on systems that are configured for a SIMOTIME environment based on the hardware, operating systems, user requirements and security requirements. Therefore, adjustments may be needed to execute the jobs and programs when transferred to a system of a different architecture or configuration.
SIMOTIME Services has experience in moving or sharing data or application processing across a variety of systems. For additional information about SIMOTIME Services or Technologies please send an e-mail to: helpdesk@simotime.com or call 415 883-6565. We appreciate hearing from you.
Software Agreement and Disclaimer
Permission to use, copy, modify and distribute this software, documentation or training material for any purpose requires a fee to be paid to SimoTime Technologies. Once the fee is received by SimoTime the latest version of the software, documentation or training material will be delivered and a license will be granted for use within an enterprise, provided the SimoTime copyright notice appear on all copies of the software. The SimoTime name or Logo may not be used in any advertising or publicity pertaining to the use of the software without the written permission of SimoTime Technologies.
SimoTime Technologies makes no warranty or representations about the suitability of the software, documentation or learning material for any purpose. It is provided "AS IS" without any expressed or implied warranty, including the implied warranties of merchantability, fitness for a particular purpose and non-infringement. SimoTime Technologies shall not be liable for any direct, indirect, special or consequential damages resulting from the loss of use, data or projects, whether in an action of contract or tort, arising out of or in connection with the use or performance of this software, documentation or training material.
Downloads and Links
This section includes links to documents with additional information that are beyond the scope and purpose of this document. The first group of documents may be available from a local system or via an Internet connection, the second group of documents will require an Internet connection.
Note: A SIMOTIME License is required for the items to be made available on a local system or server.
Current Server or Internet Access
The following links may be to the current server or to the Internet.
Note: The latest versions of the SimoTime Documents and Program Suites are available on the Internet and may be accessed using the 
icon. If a user has a SimoTime Enterprise License the Documents and Program Suites may be available on a local server and accessed using the 
icon.
Explore An Enterprise System Model that describes and demonstrates how Applications that were running on a Mainframe System and non-relational data that was located on the Mainframe System were copied and deployed in a Microsoft Windows environment with Micro Focus Enterprise Server.
Explore The Binary or COMP format for numeric data strings. This numeric structure is supported by COBOL and may be explicitly defined with the "USAGE IS COMP" or "USAGE IS BINARY" clause.
Explore The Packed-Decimal or COMP-3 format for numeric data strings. This numeric structure is supported by COBOL and may be explicitly defined with the "USAGE IS COMP-3" clause.
Explore The Zoned-Decimal format for numeric data strings. This numeric structure is the default numeric for COBOL and may be explicitly defined with the "USAGE IS DISPLAY" clause.
Explore How to Generate a Data File Convert Program using simple specification statements in a Process Control File (PCF). This link to the User Guide includes the information necessary to create a Process Control File and generate the COBOL programs that will do the actual data file conversion. The User Guide contains a list of the PCF statements that are used for the data file convert process.
Explore How to Generate a Data File Compare, Validate or Hex-Dump Program using simple specification statements in a Process Control File (PCF). This link to the User Guide includes the information necessary to create a Process Control File and generate the COBOL programs that will do a data file compare, accumulate summary totals with a record count or produce a Hex-Dump of records in a VSAM, KSDS based on a list of user-defined keys. The User Guide contains a list of the PCF statements that are used for the data file compare, validate or dump process.
Explore the COBOL Connection for more examples of COBOL programming techniques and sample code.
Explore The ASCII and EBCDIC Translation Tables. These tables are provided for individuals that need to better understand the bit structures and differences of the encoding formats.
Explore The File Status Return Codes to interpret the results of accessing VSAM data sets and/or QSAM files.
Internet Access Required
The following links will require an Internet connection.
A good place to start is The SimoTime Home Page for access to white papers, program examples and product information. This link requires an Internet Connection
Explore The Micro Focus Web Site for more information about products and services available from Micro Focus. This link requires an Internet Connection.
Explore the GnuCOBOL Technologies available from SourceForge. SourceForge is an Open Source community resource dedicated to helping open source projects be as successful as possible. GnuCOBOL (formerly OpenCOBOL) is a COBOL compiler with run time support. The compiler (cobc) translates COBOL source to executable using intermediate C, designated C compiler and linker. This link will require an Internet Connection.
Glossary of Terms
Explore the Glossary of Terms for a list of terms and definitions used in this suite of documents and white papers.
Comments or Feedback
This document was created and is maintained by SimoTime Technologies. If you have any questions, suggestions, comments or feedback please use the following contact information.
| 1. | Send an e-mail to our helpdesk. |
| 1.1. | helpdesk@simotime.com. |
| 2. | Our telephone numbers are as follows. |
| 2.1. | 1 415 763-9430 office-helpdesk |
| 2.2. | 1 415 827-7045 mobile |
We appreciate hearing from you.
Company Overview
SimoTime Technologies was founded in 1987 and is a privately owned company. We specialize in the creation and deployment of business applications using new or existing technologies and services. We have a team of individuals that understand the broad range of technologies being used in today's environments. Our customers include small businesses using Internet technologies to corporations using very large mainframe systems.
Quite often, to reach larger markets or provide a higher level of service to existing customers it requires the newer Internet technologies to work in a complementary manner with existing corporate mainframe systems. We specialize in preparing applications and the associated data that are currently residing on a single platform to be distributed across a variety of platforms.
Preparing the application programs will require the transfer of source members that will be compiled and deployed on the target platform. The data will need to be transferred between the systems and may need to be converted and validated at various stages within the process. SimoTime has the technology, services and experience to assist in the application and data management tasks involved with doing business in a multi-system environment.
Whether you want to use the Internet to expand into new market segments or as a delivery vehicle for existing business functions simply give us a call or check the web site at http://www.simotime.com
| Return-to-Top |
| Record Layout, a COBOL Copy File Analysis |
| Copyright © 1987-2019 SimoTime Technologies and Services All Rights Reserved |
| When technology complements business |
| http://www.simotime.com |