Putting High Level Assembler onto the Y disk
This section describes how to put High Level Assembler into production on the CMS Y disk (MAINT's 19E disk). If you plan to use another disk, go to Putting High Level Assembler onto a disk other than the Y disk.
- Log on to MAINT.
- Link to High Level Assembler code and access the Y disk.
Choose which access is required depending on whether you have used a minidisk or SFS.
For minidisk access:
Command Explanation link P696234J 29e 29e rr access 29e e
Access High Level Assembler code on a minidisk. access 19e f
Access CMS's Y disk. For SFS access:
Command Explanation access vmsys:P696234J.HLASM.TBUILD e
Access High Level Assembler code in an SFS directory. access 19e f
Access CMS's Y disk. - Check if a previous High Level Assembler release is present.
If the Y disk contains a previous release, then you should remove it. Migration is covered in substep 5, below. High Level Assembler code can be identified by modules with a prefix of ASMA and the HLASM module (Release 1 only).
- Move High Level Assembler to the Y disk. If you have created a saved segment for High Level Assembler, then all modules except the following five reside in the saved segment. Therefore you only need to copy these five modules with the VMFCOPY command:
- ASMADOP
- ASMAHL
- ASMA90
- ASMADOPT
- ASMAINFO
If you have not created a saved segment then all the High Level Assembler modules should be placed onto the Y disk using the VMFCOPY command.
You should copy the ASMAMAC MACLIB, whether or not you have created a saved segment for High Level Assembler.
If you have created a saved segment for High Level Assembler, use the following VMFCOPY commands:
Command vmfcopy asmadop module e = = f2 (prodid 5696234J%HLASM replace olddate
vmfcopy asmahl module e = = f2 (prodid 5696234J%HLASM replace olddate
vmfcopy asma90 module e = = f2 (prodid 5696234J%HLASM replace olddate
vmfcopy asmadopt module e = = f2 (prodid 5696234J%HLASM replace olddate
vmfcopy asmainfo module e = = f2 (prodid 5696234J%HLASM replace olddate
vmfcopy * maclib e = = f2 (prodid 5696234J%HLASM replace olddate
If you have not created a saved segment for High Level Assembler, use the following VMFCOPY commands:
Command vmfcopy * module e = = f2 (prodid 5696234J%HLASM replace olddate
vmfcopy * maclib e = = f2 (prodid 5696234J%HLASM replace olddate
Options:- replace
- Causes the output file to replace an existing file with the same file identifier.
- olddate
- Uses the date and time on each input file as the date and time of the last update of each corresponding output file.
- prodid
- Causes the VMSES PARTCAT file on the 19E disk to be updated.
- Migration from previous Assemblers.
If Release 1 of High Level Assembler has been removed then the ASMAHL MODULE must be copied to the Y disk as HLASM MODULE. This will allow z/VM® service to function correctly.
If you want to migrate from previous assemblers, you should consider the following:- HLASM MODULE in High Level Assembler Release 1 can be replaced by ASMAHL MODULE in this release of High Level Assembler.
- HASM MODULE in Assembler H can be replaced by ASMAHL MODULE in this release of High Level Assembler. However, ASMAHL MODULE does not support the NUM and STMT options.
- IEV90 MODULE in Assembler H can be replaced by the ASMA90 MODULE in this release of High Level Assembler. If you replace IEV90 MODULE with the ASMA90 MODULE, then you should also copy ASMAHL MODULE to HASM MODULE.
You can then copy them to the Y disk, using the following commands.
Command vmfcopy asmahl module e HLASM = f2 (prodid 5696234J%HLASM replace olddate
vmfcopy asmahl module e HASM = f2 (prodid 5696234J%HLASM replace olddate
vmfcopy asma90 module e IEV90 = f2 (prodid 5696234J%HLASM replace olddate
Options:- replace
- Causes the output file to replace an existing file with the same file identifier.
- olddate
- Uses the date and time on each input file as the date and time of the last update of each corresponding output file.
- Move User Exits (Optional)
User exits are supplied as sample assembler source on the LOCAL disk. If these exits are to be made generally available, they can be moved (ASMAX... ASSEMBLE) to the MAINT 19E disk, or the LOCAL disk can be made available to the users.
- Resave the CMS saved system This updates the shared Y-STAT (the saved Y disk file directory). If you have created a saved segment, it also updates the S-STAT (the saved S disk file directory) to reflect the updated SYSTEM SEGID file.
- Define named saved system
This creates a named saved system for CMS.
Command Explanation vmfsetup zvm cms
On z/VM, allows access to the SAMPNSS EXEC which resides on MAINT's 193 disk. sampnss cms
Create named saved system for CMS. - Resave the CMS system
Command Explanation ipl 190 clear parm savesys cms
Resave CMS saved system to reflect the change to the S-STAT (the saved S disk file directory).
- Define named saved system
This completes the installation process for the Y disk.