Update 1, 2016.09.26 9:45 CEST: I discovered that sub-field 2 of record F013C specifies the z/OS job type. I also learned that the job priority and job class are specified in separate records, and not in the F013C record.Update 2, 2016.09.26 14:20 CEST: After a little digging in the database, I learned that record F013C in the transport case file corresponds to column JBA_Rest in the JBA table. This field contains all additional job attributes for which a dedicated field does not already exist. Jobs already have fields for priority (JBA_Priority) and job class (JBA_JobClass), so these were apparently reused to store the corresponding z/OS job attributes.By comparing several jobs in a transport case file, I have worked out how most of z/OS-specific job attributes are specified.
https://us.v-cdn.net/5019921/uploads/editor/nu/pcadzyu9i4g4.png" width="720">
Transport Case records relevant to z/OS jobs
There are several records that appear in transport case exports of z/OS jobs. A couple of these records specify a single attribute. The F013C record specifies several attributes in sub-fields.
Transport case record
| Name of field in Java UI, Description | JBA table column
| Attribute name(s) | Corresponding XML key(s) |
---|
F009C
| Priority | JBA_Priority | PRIORITY, P
| MVS_Priority |
F011C
| Report destination (bitmap) 1=Generate on error only 2=Database 4=File
| JBA_Output | Y=yes, N=no JOBREPORT_ERROR_ONLY JOBREPORT_DB JOBREPORT_FILE
| Selected key(s) set to 1 OutputDbErr OutputDb OutputFile
|
F012C
| Job class | JBA_JobClass | JOB_CLASS, JC
| MVS_JobClass |
F013C
| Most z/OS-specific attributes. See table below.
| JBA_Rest | See below.
| See below.
|
When it appears underTJBAin the transport case file, theF013C record corresponds toJBA_Rest, the thirteenth column in theJBA table. This field is used to store additional job attributes for which a dedicated DB field does not exist. In the case of z/OS jobs, this field is used to store most z/OS-speicific job attributes. The attributes are specified in labeled sub-fields of the record.
F013CJ='4'K='6'2='9'6='UC4DEMO'P='MICHAEL'O='1,1'7="SCHENV='SEV_BTCH_DEV'"Q='S46JZ8.JCL.CNTL(UC4DEMO)
'a="'D08/APPL'"U='0'S='*ALL'T='2'V='1'R='5'W='L'
Sub-field of F013C record
| Name of field in Java UI, Description
| Attribute name | Corresponding XML key(s) |
---|
J
| Notify | MVS_NOTIFY | MVS_Notify |
K | Message class | MVS_MSGCLASS | MVS_MsgClass |
2 | Job type 8=Automation Engine (AE) 9=z/OS JCL A=JCL incl. z/OS job card C=? (not displayed in UI)
| MVS_JOBTYPE AE JCL1 JCL2 ?
| Selected key set to 1 MVS_TypeUC4, MVS_TypeJCL, MVS_TypeMVS, MVS_TypeAEJCL* |
6 | Job name | JOB_NAME, JN | MVS_JobName |
P | Program name (Actually,programmername)
| MVS_PROG_NAME | MVS_ProgName |
O | Message level | MVS_MSG_LEVEL | MVS_MsgLevel |
7 | Job parameters | MVS_JOB_PARAMS | MVS_Params |
Q | z/OS file name | JCL_SOURCE | MVS_FileName |
a | Account | MVS_ACCOUNT | MVS_Account |
U | With non-JES output (0=no, 1=yes, 2=default) | MVS_COMPLETEJOBOUT | MVS_ComplJobOut |
S | Obtain these message classes | MVS_GETMSGCLASSES | MVS_GetMsgClass |
T | Purge (0=no, 1=yes, 2=default) | MVS_JOBPURGE | MVS_PugreJob |
V | Release (0=no, 1=yes, 2=default) | MVS_RELMSGCLASS | MVS_RelMsgClass |
R | Route to these message classes | MVS_ROUTEMSGCLASS | MVS_RouteMsgClass |
W | Return code (H=highest, L=latest) | MVS_DETERMINE_RETCODE | MVS_DetermineRetcode |
For comparison, here is a similar excerpt from an XML export.
Example ATTR_MVS dictionary from XML export
<ATTR_MVS state="1">
<OutputDb>1</OutputDb>
<OutputDbErr>0</OutputDbErr>
<OutputFile>1</OutputFile>
<MVS_TypeUC4>0</MVS_TypeUC4>
<MVS_TypeJCL>1</MVS_TypeJCL>
<MVS_TypeMVS>0</MVS_TypeMVS>
<MVS_TypeAEJCL>0</MVS_TypeAEJCL>
<MVS_JobName>UC4DEMO</MVS_JobName>
<MVS_JobClass>A</MVS_JobClass>
<MVS_ProgName>MICHAEL</MVS_ProgName>
<MVS_Account>'D08/APPL'</MVS_Account>
<MVS_Priority>3</MVS_Priority>
<MVS_MsgLevel>1,1</MVS_MsgLevel>
<MVS_MsgClass>6</MVS_MsgClass>
<MVS_Notify>4</MVS_Notify>
<MVS_Params>SCHENV='SEV_BTCH_DEV'</MVS_Params>
<MVS_FileName>S46JZ8.JCL.CNTL(UC4DEMO)</MVS_FileName>
<MVS_ComplJobOut>0</MVS_ComplJobOut>
<MVS_GetMsgClass>*ALL</MVS_GetMsgClass>
<MVS_PugreJob>2</MVS_PugreJob>
<MVS_RelMsgClass>1</MVS_RelMsgClass>
<MVS_RouteMsgClass>5</MVS_RouteMsgClass>
<MVS_DetermineRetcode>L</MVS_DetermineRetcode>
</ATTR_MVS>
Can anyone confirm or correct my findings? Thanks in advance.
* z/OS job type
MVS_TypeAEJCL is undocumented. A job with this job type can be imported from XML, but the chosen setting is not displayed in the Java UI.