Were splitting hairs here.  The original question related specifically to
batch processing.  (I took this to mean JCL/Converter/Interpreter.) The
information from the link is related to tso and the tso call facility.
 There is no ASIS facility within a C/C++ program.

A C/C++ program will recieve parms as passed (subject to the PLIST(OS|HOST)
setting) and will not change the case of the passed parameters.  In fact you
can send hex values (except x'00') in a parm from JCL by turing HEX ON.

With the information you have provided we can see that the TSO has different
rules for parm processing that JCL.  Neither the TSO or JCL rules apply to
program to program calls.

Regards,
Sam

On Sun, Dec 27, 2009 at 5:38 AM, Paul Gilmartin <paulgboul...@aim.com>wrote:

> On Sun, 27 Dec 2009 04:57:25 +0000, Sam Siegel wrote:
>
> >For caps on/caps off, I was referring to ISPF edit.
> >
> That has very little to do with how JCL passes parms, nor
> how C/C++ receives them, nor with any other editor the user
> chooses because it has less restrictive conventions.
>
> More relevant, and truly dismaying, I stumbled onto:
>
> Title:  z/OS V1R10.0 XL C/C++ User's Guide
> Document Number: SC09-4767-07
>
> http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/cbcug170/11.3.2
>
> 11.3.2 Passing arguments to the z/OS XL C/C++ application
>
>  How the z/OS XL C/C++
>  program is invoked     Example                  Case of argument
>
>  By CALL command (with  CALL program Args ASIS   Mixed case (However,
>  control arguments                               if you pass the
>  ASIS                                            arguments entirely in
>                                                 upper case, the
>                                                 argument will be
>                                                 changed to lower
>                                                 case.)
>
> WTF!?
>
> Sheesh.  "ASIS" should mean ASIS.  Lower case is left lower _and_
> upper case is left upper.
>
> This is an egregious example of not fixing breakage where it
> occurred, but introducing additional breakage elsewhere with
> the misguided and futile hope that it will offset the original.
>
> -- gil
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to