The VMXAOPTS macro in HCPAC0 and the ACFFDR specify a number of important options. We supply default values for these options. Review and modify these values as appropriate. For more information about the VMXAOPTS macro, see the Systems Programmer Guide.
You can also use the ACF2VM CONFIG file to supply these options. If you respond “CONFIG” when prompted, Step 2 allows you to create/modify the ACF2VM CONFIG. If you chose this option, you should remove any old HCPAC0 text file from a previous release that you have on your 2A0 minidisk.
Before you start this step, run VMFSETUP to access the disks required to generate your CP system. For example:
Step 2 is starting. Modify VMXAOPTS and assemble HCPAC0. Enter GO to continue or ? for more information. Enter “CONFIG” to edit or create the ACF2VM CONFIG file if you are using the ACF2VM CONFIG file support to supply VMXAOPTS options.
If you respond to this question with ?, you see the following information:
Step 2 modifies VMXAOPTS and assembles HCPAC0. The VMXAOPTS macro specifies certain information about the site environment that cannot be obtained from the CA ACF2 for z/VM ACFFDR. The assembly of HCPAC0 includes this macro. Enter "CONFIG" to edit or create the ACF2VM CONFIG file if you are using the ACF2VM CONFIG file support to supply VMXAOPTS options. Reply "?" to the prompts within this step for more information. This step performs the following functions: (for VMXAOPTS) A. Prompts you to change VMXAOPTS. If you reply "NO", go to step B. If you reply "YES", CA ACF2 for z/VM issues the XEDIT command with the CTL option for HCPAC0 ASSEMBLE and displays the VMXAOPTS macro. You can then edit HCPAC0. When done, enter the xedit FILE subcommand and this exec regains control. B. Prompts you to assemble HCPAC0. If you reply "YES", CA ACF2 for z/VM issues the ACF2ASM HCPAC0 CP G command. The minidisk with CP maclibs must be accessible. This step performs the following functions: (for ACF2VM CONFIG) A. If you enter "CONFIG", you are prompted to edit or create the ACF2VM CONFIG file. If the file does not exist, you are given the option to create one starting with a sample config file. Valid replies and their meanings are: "GO" (or a null line) to continue with the installation. "CONFIG" indicates that you want to edit or create the ACF2VM CONFIG file to specify VMXAOPTS options. "COMPLETE" indicates you have completed all of the required functions this step performs. CA ACF2 for z/VM assumes that you have completed everything properly and continues to the next step. "HELP" displays information on using this exec and valid replies for all prompts. Wait for a repeat of the prompt, then enter your reply. Press ENTER when you are finished reading:
If you respond to this question with GO, you see the following information:
go Do you want to edit HCPAC0 (to modify VMXAOPTS)?. Reply YES or NO. The default is YES.
We recommend that you add CAIMAINT to the FORCEID list.
After you edit your options, the following prompt appears:
Do you want to assemble HCPAC0 ? Be sure that the minidisks with your CP maclibs are accessed. If they are not, reply "CMS" and then enter the commands to access them before replying as described below. Reply "YES" or "NO". Reply "EDIT" to re-edit HCPAC0. The default is "YES". Warning: If you reply "NO", the HCPAC0 module may be incorrect.
The prompts that CA ACF2 for z/VM displays depend on your responses to previous questions.
If you reply “CONFIG” to the Step 2 prompt, you see the following:
Enter the fileid (filename, filetype, and filemode) of your ACF2VM CONFIG file. If the file does not exist yet, you will be given the option to create the initial file from the ACF2SAMP CONFIG file. The ACF2VM CONFIG file needs to reside on the same parm disk as the SYSTEM CONFIG file. You may substitute an equal sign ("=") to take the default value for any part. For example, "= = K" would mean use the default filename and filetype with a filemode of "K". The current fileid value is: ACF2VM CONFIG K You may just press ENTER to use the current fileid (Reply "CMS" to enter CMS commands)
If the file ID you enter does not exist, Step 2 allows you to create your ACF2VM CONFIG file from a sample:
Config file ACF2VM CONFIG K not found. Do you want to create it from the ACF2SAMP CONFIG file? Reply "YES" to create file: ACF2VM CONFIG K Reply "NO" to enter a new fileid Reply "CMS" to enter CMS commands yes
You also require an imbed statement in your system config. If you do not have an imbed statement, the following warning appears:
Warning: The SYSTEM CONFIG does not appear to contain an IMBED statement to include the ACF2VM CONFIG file. You need to have the following statement: IMBED ACF2VM CONFIG in the SYSTEM CONFIG file. Do you want to xedit the the SYSTEM CONFIG file? Reply "YES" to xedit SYSTEM CONFIG K Reply "SKIP" to skip this check and continue. yes
Step 2 is complete.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|