Applying APARs

When you need to apply maintenance or fixes to the runtime environment, use the following process.

Maintenance is applied using the a JCL batch job called DFHMAINA. The JCL is very similar to the DFHMAINJ post-installation job, in that it contains a subset of the parameters from DFHMAINJ. DFHMAINA invokes a REXX program called DFHMAINX, which looks in member DFHMAINZ for a list of the changed and new members that require maintenance as part of an APAR. DFHMAINZ is updated every time maintenance is applied.
  1. Edit the DFHMAINA JCL, supplying the same parameter values as you would for DFHMAINJ. The parameters that you need to edit are:
    JOB1
    Together with JOB2 and JOB3, JOB1 is used to create the JCL JOB statements for the required jobs in the .SCIZSAMP library. Do not alter the number of + symbols at the beginning of the statement, as it used to substitute the jobname when DFHMAINJ runs.
    JOB2
    JCL JOB statement continued.
    JOB3
    JCL JOB statement continued.
    SHLQ your.smpe.install.hlq
    A 1-35 character length value that is the data set name high level qualifier of the CICS® SFR SMP/E installation libraries. This value must match what you specified in the previous step for syshlq.
    QUAL your.runtime.library.hlq
    A 1-35 character length value that is the data set name high level qualifier of the runtime libraries. This value must match what you specified in the previous step for hlqual.
    MQ YES|NO
    Indicates if you require support for WebSphere® MQSeries® (WMQ). If you specify MQ YES, then you must also define values for the HLQMQ and THE_QMGR parameters. You must specify this parameter if you want to use the Simulator program to verify your installation.
    HLQCICS your.cics.hlq
    A 1-35 character length value that is the high level qualifier of the CICS libraries.
    HLQCOBOL your.cobol.hlq
    A 1-35 character length value that is the high level qualifier of the COBOL runtime libraries.
    HLQCEE your.language.environment.hlq
    A 1-35 character length value that is the high level qualifier of the Language Environment® runtime libraries.
    WSDIR_REQ /your/wsdir/requester/
    The fully qualified name of the Web service pickup directory on HFS that contains the Web service binding file and optionally the WSDL for your Web service requester application. The length of the fully qualified directory name should not exceed 255 characters, and should start and end with a /.
    Acceptable characters:
    A-Z a-z 0-9 ./_
    The directory name is case sensitive.
    CONFIG_REQ /your/pipeline/configuration/requester_config.xml
    The name and location of the requester mode pipeline configuration file in HFS. For example, /usr/lpp/cicsts/samples/pipelines/basicsoap11requester.xml. The pipeline configuration file defines the message handlers that process outbound and inbound Web service requests for your Web service requester application. The length of the fully qualified directory name should not exceed 255 characters, and should start with a /.
    Acceptable characters:
    A-Z a-z 0-9 ./_
    The directory and file name are case sensitive.
    SHELF_REQ your/shelf/directory/
    The fully qualified name of the directory on HFS that contains subdirectories for the requester mode pipeline configuration files and Web service requester binding files. The length of the fully qualified directory name should not exceed 255 characters, and should start and end with a /.
    Acceptable characters:
    A-Z a-z 0-9 ./_
    The directory name is case sensitive.
    WSDIR_PROV /your/wsdir/provider/
    The fully qualified name of the Web service pickup directory on HFS that contains the Web service binding file and optionally the WSDL for your Web service provider application. The length of the fully qualified directory name should not exceed 255 characters, and should start and end with a /.
    Acceptable characters:
    A-Z a-z 0-9 ./_
    The directory name is case sensitive.
    CONFIG_PROV your/pipeline/configuration/provider_config.xml
    The name and location of the provider mode pipeline configuration file in HFS. For example, /usr/lpp/cicsts/samples/pipelines/basicsoap11provider.xml. The pipeline configuration file defines the message handlers that process inbound and outbound Web service requests for your Web service provider application. The length of the fully qualified directory name should not exceed 255 characters, and should start with a /.
    Acceptable characters:
    A-Z a-z 0-9 ./_
    The directory and file name are case sensitive.
    SHELF_PROV /your/shelf/directory/
    The fully qualified name of the directory on HFS that contains subdirectories for the provider mode pipeline configuration files and Web service provider binding files. The length of the fully qualified name should not exceed 255 characters, and should start and end with a /.
    Acceptable characters:
    A-Z a-z 0-9 ./_
    The directory name is case sensitive.
    PREFIX your.prefix
    A 1-7 character length value. The JCL jobname is created as a combination of this value and the name of the member that is customized. For example, if you specify PREFIX CSFR, this would rename every jobname in the members of the runtime SCIZSAMP library with CSFR as the first four characters e.g. //DFHMASET would become //CSFRASET. If you do not specify a value for this parameter, the sample jobnames are the same as the member names.
    Acceptable characters:
    A-Z a-z 0-9
    The first character of this value must not be a number.
    HLQMQ your.mq.hlq
    A 1-35 character length value that is the high level qualifier of the WMQ runtime libraries.
    Note: This parameter is required if you specified MQ YES.
    THE_QMGR qmgrname
    A 1-4 character length value that is the name of the WMQ queue manager that resources are defined to.
    Note: This parameter is required if you specified MQ YES.
    Acceptable characters:
    A-Z a-z 0-9 
    The first character of this value must be uppercase and not a number.
  2. Submit DFHMAINA. The job is validated by default. This is recommended, as any errors in the parameter values are highlighted immediately before the job runs. DFHMAINA invokes the REXX program DFHMAINX. This replaces the SCIZMAC and SCIZLOAD runtime libraries, copies the members listed in DFHMAINZ from the SMP/E SCIZSAMP library to the runtime SCIZSAMP library and customizes the members using the parameter values that you supplied in DFHMAINA.
  3. Check the output for a return code of 0. Each member that is in DFHMAINZ should have a Customizing member message associated with it in the output. You should also see the following messages in the //SYSTSPRT of the DFHMAINA job output:
    CICS SFR SCIZSAMP customization beginning    
    CICS SFR SCIZSAMP customization completed succesfully
    If you have APAR PK32131 applied, the following messages are included in the output:
    CIAI1002I SCIZSAMP customization beginning
    CIAI1011I SCIZSAMP customization ended without errors
    1. If you get a return code of 4 and the following message:
      CICS SFR SCIZSAMP no members to be customized
      no updates were made to the SCIZSAMP library. You can continue to the next step.
    2. If you get a return code of 12 and the following message:
      CICS SFR SCIZSAMP - DFHMAINX could not read member xxxxxxxx
      DFHMAINZ contains a member name that does not exist in SCIZSAMP library. xxxxxxxx is the name of the unrecognized member. Read the PTF documentation to check that the member name in question is supposed to be there. You might need to reapply the fix. If the problem still persists, contact IBM.
  4. Perform any additional steps as outlined in the APAR documentation.