IBM Support

IV70733: TWS AS400 JOBS INITIALLY ABEND DUE TO TRUNCATED JCL, RESUBMIT OK.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • AS400 jobs with a long JCL and depending on other scheduled
    jobs can get a truncated / offset JCL from other jobs with
    special (double-byte) characters. This can vary depending on
    how the job is written to the Symphony and doesn't occur every
    time.
    

Local fix

  • 1. For those job definitions in the TWS database that contain
    incorrect (double-byte) characters, modify the definitions or
    re-create fresh, new job definitions that don't have the
    problem characters.
    or...
    2. Remove the schedule containing the failing AS400 job from
    the plan (adding the ON REQUEST keyword to their definition)
    and create a script that submits them invoking sbs. In case in
    the schedule containing failing jobs there are jobs with
    special characters, the AS400 job should be submitted in a
    different schedule. This script can be scheduled to run after
    JnextPlan. In this way the schedule are added to the plan but
    in a controlled way.
    or...
    3. Use EDWA feature and create an event rule that submits the
    AS400 job in case it fails. In this case the schedules are not
    changed and the job is submitted again if it fails.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Tivoli Workload Scheduler users submitting  *
    *                  jobs containing special characters and      *
    *                  having LFTA in the network                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: In some cases the jCL submitted to the  *
    *                      LFTA is truncated (at the beginning)    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem may occur if the JCL to be submitted to LFTA is a
    long string and if there are jobs containing double-bytes
    characters in the current plan.
    The problem may occurs if the JCL string is saved in the same
    Sympony file record containing the double-byte characters. In
    this case becasue of an error in the multi-bytes character
    management at the LFTA the command is truncated.
    The code has been changed to manage multi-byte characters in the
    correct way.
    

Problem conclusion

  • Problem Conclusion
    This apar will be fixed in
    LFTA 8.6: 5TW8002
    LFTA 9.1: 5TW9001
    LFTA 9.2: 5TWA001
    LFTA 9.3: 5TWB001
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV70733

  • Reported component name

    TIV WKLD SCHDL

  • Reported component ID

    5698WKB86

  • Reported release

    8F6

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-03-09

  • Closed date

    2015-05-21

  • Last modified date

    2015-05-21

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

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

Fix information

  • Fixed component name

    TIV WKLD SCHDL

  • Fixed component ID

    5698WKB86

Applicable component levels

  • R8F6 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGSPN","label":"IBM Workload Scheduler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8F6","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
21 May 2015