IBM Support

II10169: JES2 SPOOL OFFLOAD FREQUENTLY ASKED QUESTIONS AND PROBLEMS

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

  • INTRAN

Error description

  • Question:
    I offloaded output from System A to System B. When I view
    the reloaded output ON System B the output is not displayed.
    .
    Answer:
    The spool offload facility is considered an NJE transmission
    and therefore uses the system node name to identify where to
    route the output. If the node name of System A is
    different then the
    node name of System B then the output that was reloaded to
    System B will be moved to the "output queue" and not the local
    queue.
    A   $L Jxxxx,all        display can be used
    to verify the node name of the reloaded output.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Question: I offloaded output successfully the first time but
    when I attempted the same offload again no output was offloaded.
    .
    Answer: If you have offloaded output or jobs using OFFn.JT or
    OFFn.ST these jobs will be marked as already offloaded on the
    specified device (OFFn.JT or OFFn.ST). To offload these jobs
    again with the same offload device the offload status must be
    reset for those jobs using $Tjob,OFFS=(-n) or use a different
    offloader that has not been used yet to offload the specific
    job(s).
    See JES2 Commands Manual '$T job'.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Question:When I did a spool offload operation
    not all of my output was offloaded.
    .
    Answer:Output will not be offloaded that is in operator
    hold status.    A    $L Jxxxx,all
    can be used to display the hold status. To release these holds
    issue the following:
       $TOJxxxx,all,rel=all
    In earlier JES2 XA releases issue the following:
       $TOJxxxx,all,S=Y
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Question:I offloaded jobs successfully but
    I could not reload the same jobs.
    .
    Answer:JES2 will always call the Security interface for
    each job as it enters the system from any source.
    The System doing the reload must have have the offloading
    System defined as a -- Trusted node --  even if the offloading
    system was the same system doing the reload.
    The security product must recognize the node used to offload
    as a -- Trusted Node -- . Ref info APAR    II05867
    or chapter 12 of the RACF Security Administrator Guide
    for more information.
    NOTE: A Default userid of ???????? is assigned if
    no userid is defined.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Question:I Offloaded Sysout from a Newer Version of JES2
    and when I Reloaded the output to
    an older version of JES2 the system output was purged.
    .
    Answer: You need to install APAR -- OW00284 --
    on your older version of JES2.
    A new JES2 section was added to the spool offload header.
    Without the fix on, the receiver would not recognize this
    section type so output will be deleted.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Question:I Offloaded Sysout from an early release of JES2
    (pre ESA4) and I can not reload the sysout
    to my new JES2 System.
    .
    Answer:In Pre R4xx JES2 Releases, the default for work
    selection (WS) never included the output disposition.
    The new default is   WS=(Q,OUTD/)      To reload Sysout
    that was offloaded on an older JES2 release
    you must eliminate the OUTD on the work selection.
    Issue the following: $TOFF1.SR,ws=(-OUTD/)
      you may also want to drop the 'Q' to do this ...
    Issue the following: $TOFF1.SR,ws=(-Q/)
    After these commands issue a display       $D OFF1.SR
    will show ws=(/)      (select all)
    This work selection will allow all output to be
    received (reloaded).
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II10169

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1997-01-27

  • Closed date

  • Last modified date

    2001-05-09

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
09 May 2001