3. Installation › 3.5 Generate a Database Unit › 3.5.3 Generate JCL, CLISTs, and Procedures › 3.5.3.3 Executing JCLGENC Through JCLGENG
3.5.3.3 Executing JCLGENC Through JCLGENG
After JCLGENA has executed correctly, you should check the
generated JCL output. This can be done by examining the
member prefix.MICS.CNTL(JCLGENC). If the JCL and JES
parameters are not acceptable for your installation, then
make the needed changes to prefix.MICS.PARMS members JCLDEF
or USERJCL and rerun JCLGENA. When the JCL is acceptable,
the other JCLGEN jobs are ready to run.
For example, to generate the unit's operational jobs, execute
JCLGEND. This can be done with the following SUBMIT command.
SUB 'prefix.MICS.CNTL(JCLGEND)'
The other JCLGEN jobs are submitted similarly and generate
the following groups of jobs:
JCLGENA - Database Unit Installation Jobs - Part 1
Note: JCLGENA is not generated. The COPYLIBS
job copies JCLGENA from
sharedprefix.MICS.CNTL(JCLGENA) to
prefix.MICS.CNTL(JCLGENA) when you
first create a new unit database. You
generally execute JCLGENA once to
initialize the new unit database. Once
the unit database is defined, you then
execute the JCLGENB job to recreate the
"Database Unit Installation Jobs - Part
1."
JCLGENB - Database Unit Installation Jobs - Part 1
Note: JCLGENB generates the same set of jobs
generated by the JCLGENA job. However,
the JCLGENA job is intended to be
executed only one time, when you first
define a new unit database. The
JCLGENB job is executed when ever you
need to recreate the "Database Unit
Installation Jobs - Part 1."
JCLGENC - Database Unit Installation Jobs - Part 2
JCLGEND - Database Unit Operational Jobs
JCLGENE - Jobs Affected by a DB Split After Installation
JCLGENF - SPECIAL Database Unit Installation Jobs
JCLGENG - SPECIAL Database Unit Operational Jobs
JCLGENU - Regenerate Unit Jobs from a User Supplied List
Note: JCLGENE, JCLGENF, JCLGENG, and JCLGENU are not used
during a regular CA MICS installation.