T.R | Title | User | Personal Name | Date | Lines |
---|
25.1 | Input Taken - Any code to share ? | AWARD::MAGNI | IM&T - 223-9837 | Wed Feb 17 1993 14:14 | 28 |
| Karl,
The reason we opted to return only Fatal and Success errors as a text string
was so the SYS$GETMSG call and translation would have to done by the sites.
You should not have to fiddle with strings as a fatal will not send back
a transfer price and some type of manual intervention will be needed to correct
the action.
As release 1 is complete - we will take your input for sending the
error code longword back and include it for release 2. Sites will then have
the option to either do the coding for the translation or take the following
format and code from that.
05 TPAS_TRANS_STATUS.
10 TPAS_TRANS_FACILITY_MSG PIC X(6).
10 TPAS_TRANS_DASH1 PIC X(1) VALUE "-".
10 TPAS_TRANS_PART_STATUS_CODE PIC X(1).
10 TPAS_TRANS_DASH2 PIC X(1) VALUE "-".
10 TPAS_TRANS_ERROR_MESSAGE PIC X(71).
The Facility_msg will vary from %APPIX or %SPWY. And of course the
Error_message will vary in length due to the different text. But the
STATUS_CODE will always be 1 character an F or an S.
Maybe AYR, KAO or one of the other sites has done some coding around this and
could share their code with everyone ?
Lois M.
|
25.2 | Thanks , the answer was quick, but
| KBOMFG::BRANDT | | Thu Feb 18 1993 09:47 | 11 |
| as you state in 25.1
the facility code may vary between
%APPIX
%SPWY
I'm afraid your TPAS_TRANS_FACILITY_MSG will vary
between 6 and 5 char as well
and therefore the TPAS_TRANS_PART_STATUS_CODE will have
different positions too.
-Karl
|
25.3 | we do the string manipulation to account for this | AWARD::MAGNI | IM&T - 223-9837 | Thu Feb 18 1993 14:47 | 6 |
| Karl,
We do string manipulation on the complete returned error message
so that the STATUS-CODE (F or S) will always be in the STTAUS_CODE field.
We found the SPDY during testing and changed to do string manipulation
to address this.
|