If you do: SKIP DIT, APUNLOAD will assume that you intended to SKIP ELT, as well.
If you do: SKIP ELT, APUNLOAD will also skip pulling the DIT's, Business Rules, and Cobol copybook for each ELT skipped.
Entity Relationships:
*
Figure 01 -- Entity Relationships
#
APLOAD
##
Load an Application
The APLOAD jobstream is used to load a complete MAGEC application, or multiple applications, or other dictionary data (cont.)
unloaded via APUNLOAD to the system. The input is an unloaded application's Dictionary data from the APUNLOAD (cont.)
jobstream. The input data is in 80-column text file format with numerous cross-checks built in to detect missing or out (cont.)
of order cards. The first data card must be the APLOAD control card described below if an application's definition is (cont.)
being loaded; if only dictionary data definitions are being loaded without any application definition, use the 'NULL' (cont.)
value in the APLOAD control card (columns 10-13). In either case, the APLOAD control card cannot be omitted. If the (cont.)
application being loaded is to be renamed, then the RENAME card must immediately precede the APLOAD control card. (cont.)
APLOAD will check that the data being loaded is for the proper application by comparing it against the MSK # on the (cont.)
APLOAD control card.
APLOAD will re-construct the Dictionary file records from the input file data and will add (or update) them on the (cont.)
target system's files. If a record is already on file having the same key value as the one(s) being loaded then APLOAD (cont.)
will update it, if none is already on file APLOAD will add it.
A control card option on the APLOAD control card may be specified to tell APLOAD that it is not to update any matching (cont.)
records on the target system, just add the new ones. This option is handy in the case of, let us say, the ERR file (cont.)
where you might have unloaded a range of error numbers because the ones you want are scattered throughout that range. (cont.)
You can tell APLOAD to add the new ERR records but to just bypass those which are already on the file by using the (cont.)
'NOREP' (no-replace) option. 'NOREP' tells APLOAD to not replace records currently on file, but to add those that are (cont.)
not already present.
The APLOAD jobstream has one step:
APLOAD
Load application to Dictionary.
You should also read the discussions about the APARC and APUNARC jobstreams which enable you to easily archive multiple (cont.)
versions of an application and to restore from any selected archived version on demand.
##
APLOAD Control Cards
There are two control cards accepted into the APLOAD program. The "APLOAD" card usually is passed from APUNLOAD in (cont.)
front of the unloaded data for each application (multiple applications can be loaded in a single run of APLOAD). If no (cont.)
application was unloaded (i.e. only error messages or data definitions were unloaded), there will be 'NULL' in columns (cont.)
10-13.
**
Columns
Description
1 - 9
Constant 'APLOAD '.
10 - 13
Mask (SHD) number -or- MBP number -or- 'NULL'
14 - 18
Blank or 'NOREP'.
19
Blank.
20 - 80
Up to 12 Data Class names of Dictionary files separated by commas ( , ).
If you code 'NOREP' in column 14 of the APLOAD control card then you may list up to 12 names of Data Classes (files) (cont.)
which are not to have their records updated if a record being loaded is a match. NOREP means NO REPLACE, ADD (cont.)
ONLY.
The list of valid data class names which may be on the APLOAD control card after the NOREP parameter is:
ALG  (LIB will allow replacing Custom Algorithms, but not included Lib. members)
DCL
DIT
DOC
ELT
ERR
FCD
KYF
MMP
MSK
PRM
PRO
REF
RUL
SCF
SHD
TBL
##
RENAME Control Card
Another control card may be input to the APLOAD program. It is the RENAME card. As its name implies, it alllows you to (cont.)
rename an application. If used, it must immediately precede the APLOAD card. Its format is:
Columns
Description
1 - 9
Constant 'RENAME '.
10 - 13
Old Mask (SHD) NUMBER -or- MBP number.
14
Blank, dash, or slash separator.
15 - 18
New Mask (SHD) NUMBER -or- MBP number
This enables you to unload an application, say number 801, then to load it to another system under a different name, (cont.)
say 901. You could also reload it to the original source system under a different name to create a new test copy of (cont.)
your application.
APLOAD Jobstream
    
VSE    
**
* $$ JOB JNM=APLOAD,CLASS=F
*** $$ LST CLASS=V
// JOB  APLOAD  LOAD A MAGEC APPLICATION
// EXEC PROC=MAGECLIB  -pvt. libs. & DLBL's for dictionary
// ASSGN SYS006,........  unloaded appl. from APUNLOAD
// ASSGN SYS007,SYSLST  audit trail report
// EXEC APLOAD,SIZE=(AUTO,20K)
/*
/&
* $$ EOJ
    
z/OS    
**
//APLOAD JOB (ACCT)  LOAD A MAGEC APPLICATION
**//STEP1  EXEC PGM=APLOAD
//STEPLIB DD DSN=MAGEC.LOADLIB,DISP=SHR
* * * * * * *DD's for dictionary files
//SYS006  DD DSN=....  unloaded appl. from APUNLOAD
//SYS007  DD SYSOUT=*  audit trail report
//
    
PC    
**
Edit, as necessary, the control cards found in the file named:
\MAGMF\APUNLOAD.PUN
 
At the prompt, enter:
APLOADEX
 
 
 
 
APCOPY Jobstream
**
    
VSE    
**
* $$ JOB JNM=APCOPY,CLASS=S