Reason:
TLMSVMFX determined that the number of AUX records in VMF1 exceed the warning level for AUX records in VMF2. This means that you will get warning messages from TLMS after the extend is complete.
Action:
Do not confirm the start of the VMF extend. Reformat VMF2 with more AUX records specified.
Reason:
TLMSVMFX determined that all the secondary VMF is no longer being used and “poisoned” it. The CTL record has changed to cause most TLMS programs to ABEND if they attempt to use it.
Action:
None. This is an informative message.
Reason:
TLMSVMFX determined that there are not enough AUX records defined in VMF2 to contain the AUX records used in VMF1. The VMF extend is terminated.
Action:
Reinitialize VMF2 with enough AUX records to contain those used in VMF1.
Reason:
The old VMF (VMF1) must be backed up within three hours of when the VMF extend is started. This current backup reduces the data to recover if the VMF must be restored. The VMF extend is terminated.
Action:
Back up the old VMF and restart the VMF extend.
Reason:
The MODE parameter in CAIPARM file is not valid. It can be RESET, TEST, or EXTEND. The VMF extend is terminated.
Action:
Correct the MODE parameter and restart the VMF extend.
Reason:
TLMSVMFX ABORTed due to previous errors or the ABORT command. The VMF extend terminated without ensuring that the TLMS LPARs had returned to their original state.
Action:
Contact CA support before attempting any corrective action.
Reason:
TLMSVMFX determined that a TLMS LPAR that does not have the code to support a VMF extend has started accessing the VMF while a VMF extend was in progress. If TLMSVMFX has not recataloged the VMF alias, a failure occurs and TLMSVMFX recovery returns all TLMS LPARs to their original state.
Since all LPARs are writing to the old VMF (VMF1) there is no data lost.
Action:
If this is followed by CAT6587E or CAT6588W, the VMF alias is recataloged and you should see those messages. Otherwise, the VMF extend terminates and you must upgrade LPAR xxxx before attempting another VMF extend.
Reason:
TLMSVMFX detected that a TLMS LPAR that does not have the code to support a VMF extend started accessing the secondary (old) VMF after the VMF alias was cataloged to point to the new VMF (VMF2). LPAR xxxx does not recognize the commands from TLMSVMFX so it will not switch to the new VMF. It is also not writing the new VMF.
TLMSVMFX aborted to prevent data loss. Some TLMS LPARs will be writing to both the new and old VMFs. They have some subtasks stopped and some DD statements not allocated.
Action:
Contact support immediately. Do not stop any TLMS LPARs or run TLMS utilities. If possible limit tape processing on LPAR xxxx. Retain job logs and CAIMSG data from all TLMS LPARs and CATVMFX.
Reason:
TLMSVMFX detected that a TLMS LPAR that does not have the code to support a VMF extend started accessing the VMF while a VMF extend was in progress. xxxx is the SMFID of the LPAR which started. Since LPAR xxxx is writing to the new VMF and the VMF alias has been recataloged to point to the new VMF, it is safe to continue processing. LPAR xxxx used the VMF alias to allocate the new VMF.
Action:
Do not stop the VMF extend. Upgrade the code of LPAR xxxx before running another VMF extend.
Reason:
TLMSVMFX detected that the ALIAS and VMF1 parameters in the CAIMSG file have the same data set name (DSN). If you allow the VMF extend to complete, the old VMF (VMF1) will be uncataloged and the VMF alias will be cataloged with that name.
This may be valuable for the first time you extend the VMF, because you will not need to change the VMF DSN in the JCL. Otherwise, this is probably an error.
Action:
If you do not want to use the current VMF name for the VMF alias, reply n to the CAT6592P prompt or specify STOP to the CAT6500P prompt.
Reason:
TLMSVMFX detected that the data set name specified by the VMF1 parameter and the data set name specified by the VMF2 parameter are the same. VMF2 should specify the DSN of a new VMF for TLMS to use. You must initialize this VMF and write no data to it.
Action:
Ensure that VMF1 and VMF2 do not specify the same data set name.
Reason:
TLMSVMFX detected that the data set name specified by the ALIAS parameter is the same as the VMF2 parameter. The ALIAS parameter must specify either the DSN specified by VMF1 or the DSN of a z/OS catalog ALIAS that points to the DSN specified by VMF1.
If the ALIAS DSN is the same as the VMF1 DSN, TLMSVMFX uncatalogs VMF1 and creates an alias with the same DSN. That alias points to the dataset specified by VMF2. This is not done until all TLMSs have switched to VMF2. This method may be used so that TLMS JCL will not need to be changed.
Action:
Change the ALIAS parameter.
Reason:
TLMSVMFX displays the parameter and status of the VMF. This prompt gives you a chance to verify these before starting the extend.
Action:
Reply y to continue with the VMF extend or anything else to stop the VMF extend.
Reason:
TLMSVMFX detected the LPAR xxxx stopped. Where xxxx is the SMFID of an LPAR which was actively running TLMS when VMF extend started. This is not an error but the TLMS on that LPAR will not be able to restart until TLMSVMFX has completed.
Action:
None. This is a warning message.
Reason:
TLMSVMFX detected LPAR xxxx became active before the VMF alias was recataloged and LPAR xxxx does not support the VMF extend process. xxxx is the SMFID for the LPAR.
Action:
None. This is an informative message.
Reason:
TLMSVMFX detected that LPAR xxxx started. The action taken by TLMSVMFX will be noted in later messages. xxxx is the SMFID of the LPAR.
Action:
None. This is an informative message.
Reason:
TLMSVMFX found more than 15 LPARs sharing the VMF. Because TLMSVMFX extend can only manage 15 LPARs at once, TLMSVMFX terminates without attempting the VMF extend.
Action:
Check the TLMSVMFX list of LPARs. Remove old LPARs from the VMF control record and the VMF extend rerun.
Reason:
TLMSVMFX found no active LPARs on this VMF. TLMSVMFX terminates without attempting to perform a VMF extend. TLMSVMFX is for changing VMFs while TLMS is active.
Action:
Ensure that the VMF parameter specifies the original VMF which you need to extend. Also ensure that no TLMSs are active on the VMF you want to change. Run the batch VMF utilities.
Reason:
The new VMF specified by the VMF2 parameter must be allocated, cataloged, and not initialized by CATVMFI. No other processing should be done. TLMSVMFX terminates with no attempt to extend the VMF if it is not initialized.
Action:
Run CATVMFI against the VMF specified by the VMF2 parameter. Ensure that you use the actual VMF name and not the VMF alias name.
Reason:
A VMF extend job is already running on an LPAR or a VMF extend previously aborted, leaving data in the VMF control record so that an extend appears to be in progress.
Action:
Determine if a VMF extend is running. If an extend is not running, then run CATVMFX,DO=RESET to clear the extend information from the control record.
|
Copyright © 2014 CA.
All rights reserved.
|
|