The new SET transactions have been implemented for several reasons. One of these is an internal requirement that every step in the product install needs to have a condition code 0. In the past, some CA Datacom Datadictionary steps could have condition codes greater than zero but the processing would still be valid.
Note: These transactions are effective for the DDCFBLD, DDUPDATE, and DDUTILTY batch programs.
Not all DDUPDATE condition code 8 can be treated as equal. Care has to be taken regarding which condition code 8 can be reset. If you receive condition code 8 due to not found conditions, the use of the SET NTFFN is a much better choice. Do not use the blanket SET CCn0 as a blanket reset of the condition code without prior knowledge if you think the error can be ignored or not. Use extreme prejudice when using this SET CCn0 option.
The –SET CCn0 transaction sets the condition code of the job step to 0 if an error code causes it to be set to n or less, where n can be 8, 4 or 0. If n is 0, the condition code handling is reset to the standard processing. If necessary, the –SET can be included multiple times in an input set of transactions so that specific groups of transactions can be handled as needed. The –SET CCn0 transactions would have to fall between the –END and the next header transaction (-ADD, -DEL, and so forth) or prior to the first header transaction excluding the -USR.
The SET NTFn transaction sets the external condition code to n if the occurrence specified in the header transaction is not found (NTF) where n can be 8, 4, or 0. This is useful if you precede a set of BTG or ADD transactions with a DEL/1000 OBSOLETE without knowing whether the structure is there or not. Also, if there is a generic report included and you do not know if there are any occurrences meeting the RPT transaction criteria. Again, there can be multiples of these transactions in a single execution to allow for cases where occurrences must be present and others might or might not be in the same job step. The rules for inclusion are the same as for the SET CCn0.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|