CCSID would determine which characters were treated as valid. I would not expect IDCAMS to second guess the user's InfoPrint parameters.
Ideally there should be a common print validation service and every utility would have a parameter to pass it. As long as the utilities attempt to redact "unprintable" data, they should allow the user to control that redaction, regardless of how many other places have a CCSID option. Especially a CCSID parameter documented as being applicable only to tape. How is DASD an excuse for translating characters that the user considers valid to periods? I don't care if it's legacy DASD, SYSOUT or Unix path, the user should be able to control the translation. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Paul Gilmartin [[email protected]] Sent: Saturday, December 12, 2020 7:24 PM To: [email protected] Subject: Re: Silly question - can one force IDCAMS PRINT to show printable lower case characters? 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: http://secure-web.cisco.com/1WhhAX4GjxhomdW3zmNfgT472Yr6nQhRZO040EgqFcFvPBMsDPxogfvqMO12NQs36E2Lf8gEmkDkccMSTqwEn22FDxfabOAdb9sSzzpmB-xLwJnTd8s0I4b9wVTIf0YIGlbUnRiAzzGGuj70uPltjgBdpcAQD3hM1RWi8kVLFAnzpfZI1-qtzSoC0tniJheFaqIvC82btQ5mIONuQYT_xpuDWMvGGdUjRSGL9FImMDx_75jgCFL2ZMBBktTpOE9u1wCgOPfs_9yaGHJ-C-WuKzYLleg8tqOQOg-XcMKs15NG3euVyj0GQw2OiD2ueoIZWJ7M0XyKZpOPrBTvXbLGr9WXF93UHmZ3y5NjnJZpxcjkFG8_3iC6cs8Jn3Ud4f-CCsiRjoKzqaHZ7tXHzsMIikG1gcxJ0BUwzivOPmilFUZ7RuB7rHgBZdogbSOd9bt9X/http%3A%2F%2Fwww.bitsavers.org%2Fpdf%2Fibm%2F1403%2FGA24-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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
