"Invalid" member names

Help for IBM's record-oriented filesystem VSAM, ESDS, KSDS, RRDS, LDS and Storage management Subsystems

"Invalid" member names

Postby Mirco » Thu Apr 29, 2010 3:04 pm

Hello all.

I have a question regarding member naming rules. This official manual says:
PDS member naming rules
* 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).

ISPF doesn't allow me to create a member with a name containing '-', '^', '&' or the like or rename a member to such name. BUT if I use some custom-written program that does not check the name, I can create such members without any problems, then list them with ISPF, view, edit etc. as if everything was OK.

The question is: can I assume that those "invalid" names will normally work and the naming rules are just recommendations, or should I try to avoid them and carefully validate every name in my programs to prevent them from being created?

Posts: 11
Joined: Thu Feb 11, 2010 7:13 pm
Has thanked: 0 time
Been thanked: 0 time

Re: "Invalid" member names

Postby Robert Sample » Thu Apr 29, 2010 4:52 pm

I would be very cautious about allowing anything not allowed by the official rules -- IBM usually has very solid reasons for such rules. I don't know of anything that wouldn't work, but 2 AM would be a bad time to find out that your back ups are not copying these member when your restore fails. The point is, there's likely something that doesn't work with invalid member names and without knowing what that is do you really want to take chances with them?
Robert Sample
Global moderator
Posts: 3657
Joined: Sat Dec 19, 2009 8:32 pm
Location: Dubuque, Iowa, USA
Has thanked: 1 time
Been thanked: 270 times

Re: "Invalid" member names

Postby dick scherrer » Fri Apr 30, 2010 3:08 am


should I try to avoid them and carefully validate every name in my programs to prevent them from being created?
Yes, you should make sure that nothing invalid is attempted. Many times in the past documented rules that are not in force become "real" and suddenly many things "go thud".

Just because some documented rule is not currently enforced when you run something invalid is no guarantee that it will currently work for all cases or that it will not be enforced by a fix (apar) let alone an upgrade to the system.

And when the enforcement is discovered it is quite likely that there will some other major problem that needs resolution. . .
Hope this helps,
User avatar
dick scherrer
Global moderator
Posts: 6269
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 93 times

Return to VSAM/SMS


  • Related topics
    Last post