Along those lines, does NETVIEW still use "hex" values in member
names? I wondered how that would work if it (NETVIEW) was pointed
to a PDSE. If I remember correctly it was using SVC 99 for some
of this.
Steve Thompson
On 1/5/2024 3:08 PM, Seymour J Metz wrote:
What about JES2 member names starting with $?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
________________________________________
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Steve
Beaver <0000050e0c375a14-dmarc-requ...@listserv.ua.edu>
Sent: Friday, January 5, 2024 3:06 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: allowed characters in member name
The last time I saw PDS Member names that were not A-Z 0-9 was in Endevor.
Those were/are the prior Member name backup until the package was committed
Steve
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Friday, January 5, 2024 2:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: allowed characters in member name
On Fri, 5 Jan 2024 18:33:40 +0000, Sri h Kolusu wrote:
What characters are allowed in JCL when specifying member name?
Radoslaw,
In general, PDS member naming rules are ( assuming code page 037)
• A member name cannot be longer than eight characters.
• The first member character must be either a letter or one of the
following three special characters: #, @, $.
• The remaining seven characters can be letters, numbers, or one of the
following special characters: #, @, or $.
• A PDS member name cannot contain a hyphen (-).
• A PDS member name cannot contain accented characters (à, é, è, and so
on).
The last two bullets are pleonastic.
ISPF also supports the same.
https://www.ibm.com/docs/en/zos/2.5.0?topic=types-member-name-conventions
I consider it bad design for middleware such as JCL or ISPF to impose
syntactic restrictions not present in the primitives, STOW/BLDL.
Special/national characters may differ based on the code page
Either:
o the supported code points should be specified in the Ref. or,
o the middleware should be aware of the code page and adapt
to it as ISPF does for regular expr3essions.
<https://www.ibm.com/docs/en/zos/3.1.0?topic=string-regular-expressions-string1>
I hate EBCDIC!
--
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
