IBM Support

PM25330: SCHEDULER SAMPLE JCL BBOCRTTS IS VAGUE ON SOME ASSUMPTIONS

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The comments in the sample JCL, BBOCRTTS, need to be updated
    to be clear that the tablespace assumes a database has already
    been created prior to running the createTableSpaceDB2ZOS.ddl
    script.
    Also, &TIMESTAMP does not exist in the z/OS environment, so in
    BBOCRTTS /tmp/_&TIMESTMP_ztblspc.ddl will be changed to
    /tmp/_ztblspc.ddl and a step should be added to remove
    /tmp/_ztblspc.ddl from any previous run of the same job.
    

Local fix

  • Manually rename /tmp/_&TIMESTMP_ztblspc.ddl to
    /tmp/_ztblspc.ddl in BBOCRTTS and to make sure a database has
    been created prior to trying to create the table space
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: The Schedule sample JCL BBOCRTTS is     *
    *                      vague on some assumptions               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The comments at the beginning of the sample JCL, BBOCRTTS, do
    not make it clear that it is up to the user to create the
    scheduler database prior to using the sample JCL.
    
    There are also temporary files created by this sample JCL
    that need to be removed. The string &TIMESTAMP does not exist
    in the z/OS environment,so this should be removed from the
    temporary file name.
    

Problem conclusion

  • The sample JCL, BBOCRTTS, has been updated to state that it
    assumes that the database has already been created.  The
    &TIMESTAMP text in the temporary file path name has been
    removed, and a step has been added to the end of the sample
    JCL to remove temporary files created.
    
    APAR PM25330 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.15 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM25330

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-10-27

  • Closed date

    2010-11-08

  • Last modified date

    2011-04-04

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

    PM20002

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

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK65061

       UP11/03/04 P F103

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.



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PM25330

Modified date: 04 April 2011