On Sat, 12 Dec 2020 23:40:52 +0000, Seymour J Metz wrote:
>I might believe lost in the world of 3211; the 3211 is older than IDCAMS.
>Shirley it's time to add a CCSID operand.
>
What would CCSID do? What implementation do you envision?
Would it interface to InfoPrint? Shouldn't every utility have one?
But that's redundant; it should be an option on DD SYSOUT.
DD, EXEC, and JOB already have a CCSID option. Is that enough?
And if SYSPRINT is DASD, it should just pass the data unfiltered.
BitSavers reinforces my conjecture. Something you don't want in a production
job:
www.bitsavers.org/pdf/ibm/1403/GA24-3073-8_1403_printer.pdf
Data Check (Sense Bit 4)
Data check indicates that a code in a data record sent to the printer does not
match a code in the Universal Character
Set (UCS) feature storage. Printing does not occur in the
print position to which the unmatching code applies. The entire line (except
for the data check position) OIr only a portion of the line may be printed.
Therefore, the last
printed line may contain erroneous data and/or an incomplete record. Data check
usually indicates that the UCS storage
was improperly loaded or that a data record code (other than blank or null)
does not compare to any code in the UCS storage.
Provide an operator message and exit from this error- recovery procedure. The
operator should then:
1. Accept the record and indicate that the application
program is to proceed without further retry of the
command, or
2. Restart the application program from a logical
point.
If the error persists, a call should be made to a service
representative.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
