Perhaps I could have been clearer: If, with EXEC PGM=IEBGENER, your SORT product is used (because IEBGENER is aliased to ICEGENER), you will see ICE or WER message prefixes (prefices?). If, instead, in that invocation of IEBGENER, "IEBGENER" was used (because SORT could not be used), then you will only see IEBGENER messages.
ICEGENER will invoke SORT or IEBGENER. If SORT was invoked for a successful COPY, you will get messages prefixed with ICE or WER. If IEBGENER was invoked, you get IEBGENER messages. In your particular example, if you used ICEGENER directly or if your IEBGENER is aliased to ICEGENER, an attempt will be made to use SORT, but an FB to a VB is not a COPY with no further control cards, so having attempted SORT, IEBGENER will be used. Unless asked otherwise, you won't see SORT messages in that case. To otherwise ask, so you do want to see the messages in that case (like ICE043A 3 INVALID DATA SET ATTRIBUTES: SYSUT2 RECFM - REASON CODE IS 08), or see more generally what was going on that IEBGENER was used (if it is not "obvious"), then add //SORTDIAG DD DUMMY and //SYSOUT SYSOUT=* (or equivalents) to your step. To see it in action for sure, change your EXEC PGM= to ICEGENER. You can always tell if SORT was used to complete the COPY, you will see the messages. If you don't see ICE or WER messages, IEBGENER was used. Does it really matter, then, whether your IEBGENER was aliased or not? IEBGENER messages, IEBGENER was used for a successful step - for any unsuccessful step, IEBGENER will always be used (probably for cases like your exact example, where "looking" at the control cards (none) it is a candidate for a SORT COPY, but the DCB conflict gets a SORT failure). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
