The Ship ASIS enhancement to the Package Shipment facility lets you ship outputs and backout members (and HFS files, or both) according to the backout status of the package. This means that when Ship ASIS is enabled and a package is partially or fully backed out, the Package Ship action has the following effects:
If Ship Asis is not enabled, outputs from the time the package was executed are shipped regardless of the package’s backout status.
When Ship ASIS is enabled, the user must take care to synchronize shipments to destination sites when the package is partially or fully backed out. With this feature enabled, during the execution of a package backout and backin action (including element action backout and backin), the user will receive messages in the package log. These messages list all the destinations to which the package was shipped before this backout or backin action. These messages alert the user that they may need to reship the package, because the backout or backin action has changed the package outputs. For example, sample caution messages are shown next:
PKMR632C PACKAGE WAS PREVIOUSLY SHIPPED TO THE FOLLOWING DESTINATION(S) PRIOR TO [BACK-OUT| BACK-IN] PKMR633C JDLSHIP 19DEC12 PKMR633C JDOSHIP 19DEC12 Reason: This package was shipped before the backout or backin function was executed. Multiple PKMR633C messages can appear, because one message is shown for each date and time the package was shipped to each destination. Action: You may need to reship the package now that the backout function has changed the package outputs.
To enable the Ship ASIS feature, the administrator must edit ENCOPTBL as follows, and then compile and link the table.
SHIP_OUTPUTS_ASIS=ON
ENHOPT MSGSEVERITY_PKMR632=
|
Copyright © 2014 CA.
All rights reserved.
|
|