Previous Topic: Appendix C. COMMON INSTALLATION ERRORS & CORRECTIVE ACTIONS

Next Topic: Appendix D.  PSP ONLINE INITIALIZATION

C.1 COMMON INSTALLATION ERRORS & CORRECTIVE ACTIONS

 
 Following are errors, messages, and corrective actions for
 situations that may arise during execution of the PSP refresh
 jobs.  Once the error has been corrected, resubmit the job.
 
 o  MICSDM STEP FAILS WITH USER ABEND U0998. SAS LOG CONTAINS
    MESSAGE:  ERROR ENCOUNTERED ATTEMPTING TO RETRIEVE TABLE
    STATISTICS FOR TABLE:  MWF$MAT. THE TABLE CANNOT BE FOUND.
 
    This condition occurs when the load job attempts to read
    sharedprefix.MICS.ISPTLIB(MWF$MAT).  This is an ISPF table
    that identifies product changes applied to your CA MICS
    system.  The usual cause is that PSP Online has not been
    activated properly to build MWF$MAT.  Ensure that you have
    activated PSP Online by following the instructions in
    Appendix D.
 
    It is also possible that the ISPTLIB data set used by the
    load job's ISPTLIB DD is not the same as the one used by
    PSP Online.  Review the JCL PROC executed in the MICSDM
    step and determine the name of ISPTLIB.  Enter PSP Online
    and select the CA MICS Data Sets for ISPF Applications
    panel (MWF;5;0;1).  Ensure that the CA MICS ISPF tables
    data set name is the same as that of ISPTLIB.
 
 o  PSPEXEC STEP ABENDS WITH SYSTEM SECURITY ERRORS WHEN
    TRYING TO ACCESS PSP DISTRIBUTION DATA SETS.
 
    Your site has implemented a security system that restricts
    your access to specific data set high-level qualifiers.
    To correct this problem, have your system security
    administrator give your user ID "read access" to these
    data sets.  If the current PSP distribution medium is
    tape, the high level qualifier is "CAI".
 
 o  PSPEXEC STEP ABENDS WITH ONE OF THE FOLLOWING MESSAGES IN
    THE JOB LOG:
 
    MIM4004 PGM SAS ATTEMPTING TO CHANGE RECFM....
                          - or -
    MIM4007 TASK WILL BE ABENDED BY DATASET ATTRIBUTE
    VERIFICATION
 
    CA MIM Resource Sharing for z/OS is installed at your
    site.  It intercepted the PSP load job's use of PROC PDS
    to reuse existing partitioned data sets.  To prevent the
    abend, have your CA MIM administrator add the program name
    of your SAS program product to the EXEMPT parameter list
    in the DEFAULT processing statement found in the EDIPARMS
    member of the parameter data set.
 
 o  PSPEXEC STEP FAILS WITH USER ABEND U0998. PSPLOG CONTAINS
    A MESSAGE ABOUT MISSING sharedprefix.MICS.PSP.PC.TEXT OR
    sharedprefix.MICS.PSP.CNTL.
 
    These two data sets are shipped with every new CA MICS
    system and are required by PSP Online.  They may contain
    installation instructions and JCL for optional products
    that are not shipped on the PSP.  The PSP.CNTL data set is
    also used by PSP Online as an interim holding place for
    the names of product changes that have been applied.  The
    instructions, JCL, and applied product change information
    are copied by the PSP load job and are written back to the
    data sets after their directories have been initialized.
 
    If a data set is missing, restore it from a backup or
    migration copy.  If a copy is not available, allocate a
    one-track partitioned data set using the RECFM, LRECL, and
    BLKSIZE as listed in Figure A-1 of Appendix A.1.

 o  PSPEXEC STEP FAILS WITH USER ABEND U0998.  PSPLOG CONTAINS
    THE MESSAGE:  A CRITICAL ERROR WAS DETECTED TRYING TO
    ALLOCATE TEST DATA SETS USED IN THE VALIDATION OF
    ALLOCATION PARAMETERS.
 
    One-track test data sets are allocated before any existing
    PSP data sets are deleted and before any PSP data sets are
    allocated.  This is done to validate the unit and VOLSER
    parameters prior to deletion of the PSP data sets.  An
    error was encountered during the allocation of one or more
    test data sets named in an earlier message in the PSPLOG.
    To correct this, investigate the batch PSP allocation
    parameters, PSPUNIT, PSPVOL, PSPSTORC, PSPDATAC, and
    PSPMGMTC or their ISPF panel equivalents. See the
    documentation in sections 2.2.1, 2.2.2, or 2.2.3.  Also,
    review the dynamic allocation parameters specified in
    PSPOVER.  Ensure that the information specified in each
    occurrence of VOLSER and UNIT is correct.  For more
    information on PSPOVER, see Appendix A.1.
 
 o  PSPEXEC STEP FAILS WITH USER ABEND U0998. PSPLOG CONTAINS
    THE MESSAGE:  UNEXPECTED FAILURE IN DYNAMIC ALLOCATION
    WHILE ATTEMPTING TO...
 
    All PSP data sets are dynamically allocated using SVC99.
    If SVC99 returns either a non-zero error code or a
    non-zero information code, then the code, the failing
    data set name, the DDNAME, and system messages are printed
    in PSPLOG.  One cause of this problem is the migration of
    data sets by a DASD management system.  Ensure that all
    cataloged PSP data sets are online and that none are
    migrated.  If there are no migrated data sets, review the
    codes and messages in PSPLOG and correct the errors.

 o  PSPEXEC STEP FAILS WITH USER ABEND U0998. PSPLOG CONTAINS
    THE MESSAGE:  THERE IS AT LEAST ONE UNAPPLIED PRODUCT
    CHANGE THAT IS NOT AVAILABLE IN THIS PSP DISTRIBUTION.
 
    The load job detected an unapplied product change that is
    no longer available on the current PSP distribution.
    Refer to the Product Change Status Report in the PSPRPT
    portion of the load job's output.  Find all occurrences of
    asterisks (*) for the unapplied, unavailable product
    changes and note them.  If the changes are for a product
    that you have chosen not to maintain, see Appendix A.2 and
    set the PRODEXCL parm to exclude that product.  If you
    choose not to exclude the product, contact Technical
    Support for the required corrective action.  For online
    assistance and a complete list of locations, primary
    service hours, and telephone numbers, contact Technical
    Support at http://ca.com/support.
 
 o  PSPEXEC STEP FAILS WITH USER ABEND U0998. PSPLOG CONTAINS
    A MESSAGE ABOUT DATA SETS WITH A ZERO BLOCK SIZE.
 
    PSP data sets identified in prior PSPLOG messages have a
    zero block size.  The common reasons are that they have
    been archived or migrated.  If this is the case,
    subsequent recalls could create problems with the
    application of product changes by back-leveling PSP
    libraries.
 
    There are several options to correct this condition.  If
    the data sets were migrated, check to see if your system
    has automatically recalled them.  If not, you may want to
    recall them now.  If you cannot recall them, or if they
    were not migrated, uncatalog the data sets.
 
    Note 1:  All efforts must be expended in restoring the
    sharedprefix.MICS.PSP.PC.TEXT data set.
 
    Note 2:  If either sharedprefix.MICS.PSP.CNTL or
    sharedprefix.MICS.PSP.PC.TEXT is uncataloged, you must
    allocate it as a one-track partitioned data set using the
    RECFM, LRECL, and BLKSIZE as listed in Figure A-1 of
    Appendix A.1.  Furthermore, a member named @@BAS must be
    added to the sharedprefix.MICS.PSP.PC.TEXT data set.  This
    member must contain one line that contains only 00010000
    starting in column 1.
 
 o  PSPEXEC STEP FAILS WITH USER ABEND U0998. PSPLOG CONTAINS
    A MESSAGE ABOUT A SEVERE ERROR AND NOTES THIS SAS VERSION
    IS NOT SUPPORTED BY CA MICS.
 
    The load job has been submitted using a version of SAS not
    supported by CA MICS. Contact Technical Support for the
    required corrective action.  For online assistance and a
    complete list of locations, primary service hours, and
    telephone numbers, use http://ca.com/support.
 
 o  PSP LOAD JOB ABENDS WITH AN S913 SECURITY VIOLATION
 
    Modules are written to disk by executing the program named
    LPEBLDD.  It runs as a "non-authorized" program.  Some
    mainframe security systems, such as CA Top Secret, have a
    feature that restricts non-authorized programs from
    writing authorized load modules.  (An authorized load
    module is link-edited with an attribute of AC(1)).  If
    your site has this security feature activated and is
    licensed for the CA MICS Space Collector (VCC), then the
    load job will fail with an S913 abend while trying to
    write an authorized VCC load module.  To prevent this
    abend, request your security administrator to permit
    LPEBLDD to write authorized load modules.
 
 o  STEP MICSVRAB ABENDS WITH U0998. SAS LOG CONTAINS THE
    MESSAGE:  THE TARGET CA MICS COMPLEX IS THE WRONG VERSION.
 
    In the unlikely event that you encounter an abend with
    this message, contact Technical Support.  For online
    assistance and a complete list of locations, primary
    service hours, and telephone numbers use
    http://ca.com/support.
 
 o  STEP #PCHOLD ENDS WITH CONDITION CODE 4 AND THE MESSAGE
    WARNING:  NO MEMBERS FOUND TO MATCH @@
 
    It is assumed that the original valid
    sharedprefix.MICS.PSP.PC.TEXT data set is no longer
    available and not recoverable, and an empty data set has
    been allocated to take its place.
 
    To allow the PSP refresh job to be rerun, a member named
    @@BAS must be added to the sharedprefix.MICS.PSP.PC.TEXT
    data set.  This member must contain one line that contains
    only 00010000 starting in column 1.