IBM Support

PM22802: ICAT CONFIGURE NTH FOR SEQUENTIAL OUTPUT WILL NOT ACCEPT VOLSER WITH NUMERIC FIRST CHARACTER

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When configuring Near Term History for seqential output, if the
    volser specified for the sequential dataset does not begin with
    an alphabetic character, a pop up is returned indicating that
    the volser is invalid.
    
    Panel KD261PZ1 allows the customer to configure sequential
    datasets for output by Near Term History. If the volser does not
    start with an alphabetic character, a short message < Invalid
    Name > is displayed. If PF1 ( help ) is pressed, a pop up is
    presented that reads
    Enter up to 8 alphanumeric
    characters (first cannot be
    numeric).
    
    
    NTH NTA Near term accounting vsamseq RKD2SQ01 seq
    

Local fix

  • Comment out the following
    TKANCUS(KD261PZ1) does the following VERs on the sequential
    volser
    VER (&H2SEQVL1,NAME)
    VER (&H2SEQVL2,NAME)
    VER (&H2SEQVL3,NAME)
    VER (&H2SEQVL4,NAME)
    VER (&H2SEQVL5,NAME)
    VER (&H2SEQVL6,NAME)
    VER (&H2SEQVL7,NAME)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component:                          *
    *                 -   ICAT                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Configuring NTH for static sequential   *
    *                      output in ICAT will not accept VOLSER   *
    *                      with numeric first character            *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    *                                                              *
    ****************************************************************
    PROBLEM SUMMARY:
    VOLSER values are validated using a predefined pattern that does
    not accept a numeric first character.
    
    PROBLEM CONCLUSION:
    The pattern that is used for the validation was changed in a way
    that it now accepts all valid VOLSER values.
    

Problem conclusion

  • The pattern that is used for the validation was changed in a way
    that it now accepts all valid VOLSER values.
    
    KEYWORDS : ICAT NTH SEQUENTIAL VOLSER
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM22802

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    420

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-09-20

  • Closed date

    2010-12-13

  • Last modified date

    2011-01-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UK63029

Modules/Macros

  • KD261PZ1
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R420 PSY UK63029

       UP10/12/17 P F012

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
03 January 2011