ubject: Re: allowed characters in member name
On Mon, 8 Jan 2024 11:00:38 -, Lennie Dymoke-Bradshaw wrote:
>Using quotes around the DSNAME will allow any combination of Hex chars for a
>Dsname I think (possibly excluding 44X'04' which represents the VTOC). However
>these are not su
Subject: Re: allowed characters in member name
Why the use of data set names enclosed with apostrophes, that are
not TSO oriented?
Back in the days when I was doing DOS to MVS migrations, to
access certain DOS data sets, you needed this because they could
contain names like this:
'PAYROLL STR
Why the use of data set names enclosed with apostrophes, that are
not TSO oriented?
Back in the days when I was doing DOS to MVS migrations, to
access certain DOS data sets, you needed this because they could
contain names like this:
'PAYROLL STR 12MAY75' for either a Tape label or disk
On Mon, 8 Jan 2024 11:00:38 -, Lennie Dymoke-Bradshaw wrote:
>Using quotes around the DSNAME will allow any combination of Hex chars for a
>Dsname I think (possibly excluding 44X'04' which represents the VTOC). However
>these are not supported for SMS datasets, nor can they be catalogued,
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu>
Sent: Sunday, January 7, 2024 7:34 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: allowed characters in member name
On Sun, 7 Jan 2024 23:42:41 +, Seymour J Metz wrote:
>
<050e0c375a14-dmarc-requ...@listserv.ua.edu>
Sent: Sunday, January 7, 2024 7:42 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: allowed characters in member name
Actually STOW 8XL’FF’
Will work
Sent from my iPhone
No one said I could type with one thumb
> On Jan 7, 2024, at 18:34, Paul
: Sunday, January 7, 2024 8:16 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: allowed characters in member name
Going back to hazy memories...
GDGs needed the DSN specified, and the DCB info DCB=(dsn,) so
that the allocation routines would correctly set the DSCB info
for the data set by getting
W dniu 08.01.2024 o 05:01, Paul Gilmartin pisze:
On Mon, 8 Jan 2024 03:42:05 +, Gibney, Dave wrote:
Before LIKE, you needed IDCAMS to create VSAM files, after LIKE you could do
this with just JCL
Ah. So for PS or PO it has no advantage over DCB=dsname. Perhaps for SPACE?
A lot of
W dniu 07.01.2024 o 21:55, Paul Gilmartin pisze:
On Sun, 7 Jan 2024 21:04:48 +0100, Radoslaw Skorupka wrote:
...
I have to admit: I almost never used DCB keyword in JCL and (AFAIR)
absolutely never DCB=HLQ.DATASET.NAME.
When teaching JCL I explain it, but also advice to not using that.
BTW:
2024 23:43
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: allowed characters in member name
Long ago (in OS/390?) IBM introduced a bunch of keywords equivalent to
subparameters of DCB, e.g., LRECL= is equivalent to DCB=LRECL=. I believe that
LIKE= was part of that.
--
Shmuel (Seymour J.) Metz
http
On Behalf Of
Leonard D Woren
Sent: 08 January 2024 06:29
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: allowed characters in member name
I don't think anyone has mentioned that X'C0' (left brace in the U.S.) is valid
in a member name. I didn't test to see whether it's allowed in the first
position
I don't think anyone has mentioned that X'C0' (left brace in the U.S.)
is valid in a member name. I didn't test to see whether it's allowed
in the first position; probably not.
X'C0' is also valid in a dsname on a non-SMS volume, but it's now
broken in that you can't catalog it any more.
High values indicates end of directory.
On Sun, Jan 7, 2024 at 6:30 PM Phil Smith III wrote:
> Paul Gilmartin wrote:
> >STOW 'Abc Xyz!'probably works.
> >STOW 8X'FF' probably doesn't or produces unexpected results.
>
> Ah.this is in reference to the original question, sorta, not
On Mon, 8 Jan 2024 03:42:05 +, Gibney, Dave wrote:
>Before LIKE, you needed IDCAMS to create VSAM files, after LIKE you could do
>this with just JCL
>
Ah. So for PS or PO it has no advantage over DCB=dsname. Perhaps for SPACE?
--
Thanks,
gil
bject: Re: allowed characters in member name
>
> [EXTERNAL EMAIL]
>
> On Sun, 7 Jan 2024 23:42:41 +, Seymour J Metz wrote:
>
> >Long ago (in OS/390?) IBM introduced a bunch of keywords equivalent to
> subparameters of DCB, e.g., LRECL= is equivalent to DCB=LRECL=. I believe tha
Going back to hazy memories...
GDGs needed the DSN specified, and the DCB info DCB=(dsn,) so
that the allocation routines would correctly set the DSCB info
for the data set by getting the LRECL, RECFM, etc. so that
allocation would have all that. I'm not sure that DFP V3 fixed
this, or
Actually STOW 8XL’FF’
Will work
Sent from my iPhone
No one said I could type with one thumb
> On Jan 7, 2024, at 18:34, Paul Gilmartin
> <042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:
>
> On Sun, 7 Jan 2024 23:42:41 +, Seymour J Metz wrote:
>
>> Long ago (in OS/390?) IBM
On Sun, 7 Jan 2024 19:29:46 -0500, Phil Smith III wrote:
>Paul Gilmartin wrote:
>>STOW 'Abc Xyz!'probably works.
>>STOW 8X'FF' probably doesn't or produces unexpected results.
>
>Ah.this is in reference to the original question, sorta, not to my "Why?"
>question. Thanks.
>
As
On Sun, 7 Jan 2024 23:42:41 +, Seymour J Metz wrote:
>Long ago (in OS/390?) IBM introduced a bunch of keywords equivalent to
>subparameters of DCB, e.g., LRECL= is equivalent to DCB=LRECL=. I believe that
>LIKE= was part of that.
>
Did LIKE add any expressive power that DCB lacks?
I
Paul Gilmartin wrote:
>STOW 'Abc Xyz!'probably works.
>STOW 8X'FF' probably doesn't or produces unexpected results.
Ah.this is in reference to the original question, sorta, not to my "Why?"
question. Thanks.
--
<042bfe9c879d-dmarc-requ...@listserv.ua.edu>
Sent: Sunday, January 7, 2024 6:47 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: allowed characters in member name
On Sun, 7 Jan 2024 18:16:32 -0500, Phil Smith III wrote:
>
>And Steve Beaver added:
>>The simplest path on this di
On Sun, 7 Jan 2024 18:16:32 -0500, Phil Smith III wrote:
>
>And Steve Beaver added:
>>The simplest path on this discussion is to try it in batch or ispf. The only
>>other way is in HLASM with the STOW macro
>
>Try what? Unclear what you're suggesting?
>
STOW 'Abc Xyz!'probably works.
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu>
Sent: Sunday, January 7, 2024 5:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: allowed characters in member name
On Sun, 7 Jan 2024 21:50:07
Radoslaw Skorupka wrote:
>The "8 characters rule" is widely used in z/OS and mainframe world.
>Why?
Presumably because a doubleword is a nice, discrete size of data-big enough to
be useful, small enough to manipulate with things like two (now one) register?
And Steve Beaver added:
>The simplest
DCB was often used in referbacks, eg DCB=(*.STEP1.MASTER), I'm sure most
modernspeak prefers LIKE. Blame the Beatles.
Yanno what I mean like?
On Mon, Jan 8, 2024 at 9:15 AM Paul Gilmartin <
042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:
> On Sun, 7 Jan 2024 21:50:07 +, Gibney, Dave
On Sun, 7 Jan 2024 21:50:07 +, Gibney, Dave wrote:
>DCB for the subparameters as been depreciated and, in my opinion, bad form for
>most of the 40 years I worked on mainframes. The DCB=modeldscb form used for
>new GDS allocations hasn't been needed since SMS came along. Early 90s'?
>I may
.
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Paul Gilmartin
> Sent: Sunday, January 7, 2024 12:56 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: allowed characters in member name
>
> [EXTERNAL EMAIL]
>
> On Sun, 7 Jan 2024 21:04:48
On Sun, 7 Jan 2024 21:04:48 +0100, Radoslaw Skorupka wrote:
>...
>I have to admit: I almost never used DCB keyword in JCL and (AFAIR)
>absolutely never DCB=HLQ.DATASET.NAME.
>When teaching JCL I explain it, but also advice to not using that.
>BTW: LIKE=HLQ.FOO-BAR works like a charm.
>
in
On Sun, 7 Jan 2024 13:59:09 -0600, Steve Beaver wrote:
>The simplest path on this discussion is to try it in batch or ispf. The only
>other way is in HLASM with the STOW macro
>
I've tried it with STOW. It likes any 8 bytes: lower case, embedded spaces,
NULs, etc.
And I consider it improper
W dniu 06.01.2024 o 23:59, Paul Gilmartin pisze:
On Sat, 6 Jan 2024 23:14:28 +0100, Radoslaw Skorupka wrote:
...
For dataset names the addition is "-". This character can be used in
dataset names with no tricks like name in apostrophes, uncataloged ones,
etc.
But not, in my experience, in
The simplest path on this discussion is to try it in batch or ispf. The only
other way is in HLASM with the STOW macro
Sent from my iPhone
No one said I could type with one thumb
> On Jan 7, 2024, at 13:55, Radoslaw Skorupka
> <0471ebeac275-dmarc-requ...@listserv.ua.edu> wrote:
>
> W
W dniu 07.01.2024 o 19:02, Phil Smith III pisze:
Paul Gilmartin wrote, in part, in answer to "Why can't a data set name element start
with a digit":
Left-to-right lexical analyzer that treats anything beginning with a digit
as a number.
I'm willing to believe this, but am unclear on why
No, it is not catalog issue, including multilevel alias. I just created
alias named HLQ.A-L1
However first qualifier is special one because of RACF. You cannot
create RACF profile without creating group or user for HLQ. And both
GROUP and USER names cannot contain "-".
Of course one may
Paul Gilmartin wrote, in part, in answer to "Why can't a data set name element
start with a digit":
>Left-to-right lexical analyzer that treats anything beginning with a digit
>as a number.
I'm willing to believe this, but am unclear on why whatever is parsing a DSN
would care whether it's a
And for multi-level aliases also?
Michael
At 07:15 PM 1/6/2024, Steve Thompson wrote:
Content-Transfer-Encoding: 7bit
Would that be because of a Catalog issue? As in an Alias can't contain "-"?
Steve Thompson
On 1/6/2024 6:18 PM, Ed Jaffe wrote:
On 1/6/2024 2:14 PM, Radoslaw Skorupka
Subject: Re: allowed characters in member name
Has anyone ever understood why data set/member names cannot start with
numerics? Just curious, as it seems like an odd restriction.
--
For IBM-MAIN subscribe / signoff / archive access
On Sat, 6 Jan 2024 21:11:23 -0500, Phil Smith III wrote:
>Has anyone ever understood why data set/member names cannot start with
>numerics? Just curious, as it seems like an odd restriction.
>
Left-to-right lexical analyzer that treats anything beginning with a digit
as a number.
Does the same
Has anyone ever understood why data set/member names cannot start with
numerics? Just curious, as it seems like an odd restriction.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
Would that be because of a Catalog issue? As in an Alias can't
contain "-"?
Steve Thompson
On 1/6/2024 6:18 PM, Ed Jaffe wrote:
On 1/6/2024 2:14 PM, Radoslaw Skorupka wrote:
For dataset names the addition is "-". This character can be
used in dataset names with no tricks like name in
On Sat, 6 Jan 2024 18:14:54 -0500, Tony Thigpen wrote:
>The restriction in the DCB is due to Assembler restrictions on use of '-'.
>
Explain in more detail how DCB=HLQ.FOO-BAR runs afoul of
"Assembler restrictions on use of '-'", please.
Does the JCL converter invoke Assembler to process DD
On 1/6/2024 2:14 PM, Radoslaw Skorupka wrote:
For dataset names the addition is "-". This character can be used in
dataset names with no tricks like name in apostrophes, uncataloged
ones, etc.
We tried using this for our PHX-BDT product. It worked great in the
second qualifier (e.g.,
The restriction in the DCB is due to Assembler restrictions on use of '-'.
Tony Thigpen
Paul Gilmartin wrote on 1/6/24 5:59 PM:
On Sat, 6 Jan 2024 23:14:28 +0100, Radoslaw Skorupka wrote:
...
For dataset names the addition is "-". This character can be used in
dataset names with no tricks
On Sat, 6 Jan 2024 23:14:28 +0100, Radoslaw Skorupka wrote:
>...
>For dataset names the addition is "-". This character can be used in
>dataset names with no tricks like name in apostrophes, uncataloged ones,
>etc.
>
But not, in my experience, in a reference to define DCB subparameters such
martin
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 +, Sri h Kolusu wrote:
What characters are allowed in JCL when specifying member name?
Radoslaw,
In general, PDS member naming rule
DSN with quotes is not edited at all, and is not cataloged.
On Sat, Jan 6, 2024 at 2:49 PM Jon Perryman wrote:
> On Fri, 5 Jan 2024 20:40:00 +, Nash, Jonathan S. <
> jonathan.s.n...@ssa.gov> wrote:
>
> >We have a PDSE with member names starting with a
> >left paren which were created with
On Fri, 5 Jan 2024 20:40:00 +, Nash, Jonathan S.
wrote:
>We have a PDSE with member names starting with a
>left paren which were created with some old software.
Did IBM fix this with JCL DSN= using quoted dataset and member name? My guess
is no. DSN and member name validation can be
: allowed characters in member name
Radoslaw,
From memory, this is simply the ALPHANUMNAT set. Alphabetic chars (upper
case), Numerics and the national chars (#$@). First char may not be numeric.
Lennie
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Radoslaw Skorupka
, January 05, 2024 12:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: allowed characters in member name
Radoslaw,
From memory, this is simply the ALPHANUMNAT set. Alphabetic chars (upper case),
Numerics and the national chars (#$@). First char may not be numeric.
Lennie
-Original
gt;
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 Messag
equ...@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
: 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 +, Sri h Kolusu wrote:
>>> What characters are allowed in JCL when specifying member name?
>
>Radoslaw,
>In general, PDS member naming rules a
On Fri, 5 Jan 2024 18:33:40 +, 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
>> 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
Radoslaw,
>From memory, this is simply the ALPHANUMNAT set. Alphabetic chars (upper
>case), Numerics and the national chars (#$@). First char may not be numeric.
Lennie
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Radoslaw Skorupka
Sent: 05 January 2024 17:18
To:
54 matches
Mail list logo
