QUEUE Command Converting Hex Character

[LaryBlake]

Building JCL to submit to JES on a mainframe to define new users to our applications. It all works well with one exception. One of the parameters for an application requires X'10' in the 14th position of the record. I read the record in from a file where the character is x'10', QUEUE that record as part of the JCL build process and then issue a "SUBMIT *" after all the QUEUE commands. When I look at that character in JES, it is x'50'. If I try x'20', it becomes a x'60', x'30' becomes x'70'. x'40 or 50 or 60 or 70' do not change. x'80' becomes x'C0', x'90' becomes x'D0'. Would anyone know how I could get the x'10' through to JES without the conversion to x'50'? I don't know if it's me or just the nature of REXX, and I can't use it to pass x'10' on to JES. As stated above, all works fine...it's just that a x'50' causes options to be set which I don't want, like update permissions, the x'10' only allows for read permissions within this particular product. Any ideas or clues or suggestions?

 

[superk01]

Well, obviously, TSO SUBMIT is converting the non-display (i.e. transparent) characters to other values. I don't see anything in the command documentation to prevent that. Have you considered NOT using TSO SUMBIT and trying another method? I noticed that this doesn't happen with an ISPF Edit SUB command, and it probably won't happen if you just route the jobstream directly to the JES Internal Reader.

 

[LaryBlake]

I will give those other 2 options a try. Thank you!

 

[LaryBlake]

For the record, the JCL is now being submitted with the x'10' as I wanted. The "TSO SUBMIT *" of the stack directly failed, but when I did an "EXECIO * DISKW...." of the stack to a file, and then did a "TSO SUBMIT" of the file, it was fine!