Charles: My friend, perfect. My issue is we are passing Security Sub System commands ( RACF, etc. ) thru r_radmin service call and we just started supporting mixed-case passwords, etc. The other thing that hit me was what 'setropts' was set to and how I have to query it...but i will get there..
Scott On Sun, Jan 15, 2017 at 3:07 PM, Charles Mills <[email protected]> wrote: > I don't believe COBOL inherently does any conversion whatsoever of PIC X > data. If you read in a record with PIC X data, it will remain as-is unless > you explicitly modify it in the COBOL. You may pass in the LINKAGE SECTION > PIC X data and it will not inherently be inspected or altered. It is not > uncommon in COBOL to redefine some other data type (COMP-3, for example) as > PIC X. The mere declaration of the data as PIC x does not cause COBOL to > alter it. > > Does that answer your question? > > Charles > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of scott Ford > Sent: Sunday, January 15, 2017 11:57 AM > To: [email protected] > Subject: Case Question > > All: > > I have a TCPIP inbound message that can contain mixed-cased letters. This > request is pass onto to an Assembler module calling RACROUTES to perform > authentication. > My question is this the Cobol fields in the caller are PIC X(xxx) and i > want to guarantee mixed case preservation. The called program is Assembler > ..Do i want to change the PIC X to something else ??? > > ---------------------------------------------------------------------- > 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
