Method 3: Install High Level Assembler using a batch job
The batch installation job stream for installing High Level Assembler
uses the MSHP
system history file that already exists
as part of the z/VSE® system.
This system history file might already be defined in the system standard
labels; if not, make sure that DLBL
and EXTENT
statements,
with the necessary information for the system history file, are included
in the job stream.
Depending on how you request the High Level Assembler product, you might receive different installation tapes. One might contain only the High Level Assembler product, the other might be a V2 Format tape containing one or more optional program products. The job that is shown in Figure 1 handles both types of tape (V2 Format and V1 Format).
Create and tailor the following job stream, mount the distribution tape, and run the installation job.
Figure 1 provides the JCL required to install High Level Assembler. Tailor this JCL to suit the requirements at your site.
// JOB ASMAINST
* INSTALL THE High Level Assembler LIBRARY
// OPTION LOG
* Label for High Level Assembler Library 1
* Assign install tape as SYS006 2
// ASSGN SYS006,cuu
// MTC REW,SYS006
* ----------------------------------------
* This step installs High Level Assembler
* from the distribution tape
* using the VSE system history file 3
* ----------------------------------------
// EXEC MSHP,SIZE=900K,PARM='PIDSTACKED'
INSTALL PROD FROMTAPE ID='HLASM......1.6.0' -
PROD INTO=PRD1.BASE
/*
* ----------------------------------------
* List the High Level Assembler Library 4
* --------------------------------------
// EXEC LIBR
LISTDIR SUBLIB=PRD1.BASE -
OUTPUT=NORMAL -
UNIT=SYSLST
/*
* ------------------------------------------
* Retrace the High Level Assembler product 5
* ------------------------------------------
// EXEC MSHP,SIZE=900K
RETRACE COMPONENT IDENTIFIER=5696-234-00
/*
// MTC RUN,SYS006
/*
/&
- Specify the Label Information
In area 1 , if you are installing High Level Assembler into a sublibrary other than the default then insert
DLBL, EXTENT, and ASSGN
information as specified in Figure 3. The library name must match the name that is used in the allocation job in Figure 3.There is no
DLBL
statement for the system history file. Typically it has a permanent system standard label for this, withIJSYSHF
as the file name. (IJSYSHF
is the default file name thatMSHP
looks for in a label statement.) - Assign the Distribution Tape Assign the distribution tape in area 2 to logical unit
SYS006
. Replace cuu with the address of the tape drive on which the distribution tape is mounted. Alternatively you can use the generic tape assignment:// ASSGN SYS006,TAPE
- Install High Level Assembler
Area 3 of the job calls
MSHP
to install High Level Assembler into the library and sublibrary that is identified on theINTO
operand of theINSTALL
statement. If you are installing High Level Assembler into a library and sublibrary other than the default, then change the name of the library and sublibrary on theINTO
operand of the INSTALL statement to reflect the values you specified in area 3 . For more information about the install options, refer to z/VSE: System Control Statements. - List the Directory Entries
The step in area 4 of the job lists the directory entries of the sublibrary where High Level Assembler was installed. Remove this step if a directory list is not required. If you have installed High Level Assembler into a sublibrary other than the default, then the name of the sublibrary must be changed to reflect the value you specified in area 3 .
Entries for High Level Assembler have a four character prefix of ASMA to distinguish them from other products; there are three exceptions to this rule:HD234689.Z
$SVAASMA.PHASE
$SVAASMA.OBJ
- Retrace the High Level Assembler product in the system history file.
The final step in area 5 of the job prints the component records from the system history file for High Level Assembler. Remove this step if a retrace listing is not required.
If this job must run again, remember first to restore the system history file, which should have been backed up before you run this install job, and second to run the library allocation step again, if applicable.