On 9 Aug 2013 17:02:54 -0700, in bit.listserv.ibm-main you wrote: >Yes I'm familiar with #pragma map and I use it for CEEBINT LE user exits. >It may be preferable to COBOL programmer who prefer 8 char names because of >inertia but I personally would prefer to use mixed case long names.
Most COBOL programs only deal with things in the classic z/OS data sets which for programs and copy members must have 8 character names. I kept using upper case only when working because of the problem with alpha numeric literals and compares. Limiting data to upper case only probably doesn't cut it any more but it simplifies the compares and allows use of code that generates CLC and CLI. Allowing for lower case and culturally sensitive sorting (dictionary rules apparently differ from telephone book rules) immediately involves complex subroutines. I would have liked subroutine, program and job names at least 15 characters long or the standard COBOL 30 characters but MVS and z/OS get upset with them outside of the Unix world. Clark Morris > >On 10/08/2013, at 7:52 AM, Bernd Oppolzer <bernd.oppol...@t-online.de> wrote: > >> Normally, if you compile C sources you got from "somewhere" on z/OS >> using the more classical compiler options, this is no problem, unless you >> have external function names that are longer than 8 characters and that >> don't differ in their first 8 characters, and for such situations, #pragma >> map >> is the perfect solution. For example: >> >> #ifdef XML_PRAGMA >> >> #pragma map (xml_alloc , "XMLXALLO") >> #pragma map (xml_free , "XMLXFREE") >> #pragma map (xml_realloc , "XMLXREAL") >> #pragma map (xml_freeall , "XMLXFALL") >> #pragma map (xmlp_open , "XMLPOPEN") >> #pragma map (xml_parser , "XMLPPARS") >> #pragma map (xmlp_outsymbol , "XMLPOUTS") >> #pragma map (xmlp_error , "XMLPERRO") >> #pragma map (xmlp_ftext , "XMLPFTXT") >> #pragma map (xmlp_fehltab , "XMLPFTAB") >> #pragma map (xmlp_listing , "XMLPLIST") >> #pragma map (xmlp_close , "XMLPCLOS") >> #pragma map (xmlp_reparse , "XMLPREPA") >> >> #pragma map (xmld_serialize , "XMLDSERI") >> #pragma map (xmld_freeNodes , "XMLDFRND") >> #pragma map (xmld_appendNode , "XMLDAPND") >> #pragma map (xmld_deleteNode , "XMLDDNOD") >> #pragma map (xmld_deleteChilds , "XMLDDCHI") >> #pragma map (xmld_deleteAttribs , "XMLDDATT") >> #pragma map (xmld_deleteOneAttrib , "XMLDDOAT") >> #pragma map (xmld_copyNode , "XMLDCPND") >> #pragma map (xmld_parser , "XMLDPARS") >> #pragma map (xmld_printNode , "XMLDPRND") >> #pragma map (xmld_createNode , "XMLDCRND") >> #pragma map (xmld_createAttrib , "XMLDCRAT") >> >> #endif >> >> this way, the linker gets old fashion names which it can handle >> without problems, and you don't need to do further changes >> to the C source. >> >> Kind regards >> >> Bernd >> >> >> >> Am 10.08.2013 01:35, schrieb Paul Gilmartin: >>> On Sat, 10 Aug 2013 07:29:44 +0800, David Crayford wrote: >>> >>>> Does COBOL support GOFF so you can just use the long names? Seems like a >>>> lot of unnecessary work shortening names. Uppercase can be done by the >>>> binder UPCASE option. >>> If this is the upper case option I've encountered, it makes things worse >>> rather >>> than better. BTDT; I must supply MIXED to get things to work. There >>> should >>> never have been such an option as UPPER; MIXED is entirely compatible with >>> the classic Linkage Editor. >>> >>> -- gil >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
