I am wondering if anyone else thinks that it might be useful for IBM to make an enhancement to BSAM/QSAM support for the CCSID parameter in JCL.
ref: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2b6a0/12.9 <quote> Purpose You can request the access method to convert data between the coded character set identifier (CCSID) specified on the JOB or EXEC statement and the CCSID specified on the DD statement. Data conversion is supported on access to ISO/ANSI Version 4 tapes using access methods BSAM or QSAM, but not using EXCP. <quote/> Why does this only support ASCII tapes? Would it be helpful to generalize it to any data source read or written by BSAM/QSAM? Of course, this is only of use for "pure text" data sets. But it might address the recent thread on FTP'ing a VB data set, keeping the LLBB field intact but translating the "data" portion to ASCII. Just another stupid idea, I guess. -- Schrodinger's backup: The condition of any backup is unknown until a restore is attempted. Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be. He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
