Re: Network not working between zOS and zVM

[Alan Altmark]

On Thu, 4 Jan 2024 18:44:10 +0100, Alain Benvéniste  
wrote:

>I have removed the ethernet word on link statement. 
>
>And it works ! Thanks !

You're welcome, but I don't know why it worked.  Within OSA, layer 2 and layer 
3 can communicate (unlike HiperSockets) unless port isolation is turned on in 
the IP configuration.

>What would be the impact if i start a z/os and a z/vm test environnement ? 
>Ethernet word will not be required ?

The "ETHERNET" keyword tells the device driver to use "layer 2" protocol.  That 
is, the driver will provide full ethernet frames, with MAC headers.  Without 
ETHERNET, it defaults to "IP" which is also known as "layer 3", in which the 
driver provides only IP packets, not ethernet frames, and the OSA takes care of 
adding the MAC headers. 

Alan Altmark
IBM

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Leonard D Woren]

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.  Get "NOT CATLGD 9". 
Again, I didn't try it in the first position which almost certainly is 
not allowed.



Regarding the limit of 8 characters between periods in a dsname, that 
was a requirement in OS CVOL days.  Seems to me that that validity 
test can and should be removed now that CVOLs are long long dead 
dead.  I could see requiring any levels in an MLA alias restricted to 
8 characters.  Why is left as an exercise to the reader.



/Leonard




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Mike Schwab]

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 to my "Why?"
> question. Thanks.
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Paul Gilmartin]

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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Gibney, Dave]

Before LIKE, you needed IDCAMS to create VSAM files, after LIKE you could do 
this with just JCL

> -Original Message-
> From: IBM Mainframe Discussion List  On
> Behalf Of Paul Gilmartin
> Sent: Sunday, January 7, 2024 4:35 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: 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 that
> LIKE= was part of that.
> >
> Did LIKE add any expressive power that DCB lacks?
> 
> I believe neither DCB nor LIKE can be used in nor refer to DD PATH=
> 
> The alternative might be to use JCL symbols for common attribute strings.
> 
> Combining brevity and mnemonic value:
> Q = "'"
> QQ = '"'
> 
> Don't forget to mention them in PROCEDURE EXPOSE.
> SIGNAL ON NOVALUE would remind you, if you chose to use it.
> 
> --
> 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

Re: allowed characters in member name

[Steve Thompson]

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 SMS or what. But I remember having to remember to do 
these things back in the day, for SMF tapes and the like, when 
doing the initial allocation for a GDG generation data set (GDS) 
(+1, etc.).


Steve Thompson

On 1/7/2024 5:15 PM, Paul Gilmartin wrote:

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 recall wrong, but I think LIKE was new with SMS.


Formerly needed; now deprecated.  Why was it ever needed?  I suspect the change
was less to accommodate SMS than UNIX files, which support attributes but no 
DCB.

Answering my earlier question (IRTFM):

 Example 2
 //SMSDS7  DD  DSNAME=MYDS7.PGM,LIKE=MYDSCAT.PGM,DISP=(NEW,KEEP),
 //  LRECL=1024
 In the example, the data set attributes used for MYDS7.PGM are obtained 
from
 the cataloged model data set MYDSCAT.PGM. Also, the logical record length 
of
 1024 overrides the logical record length obtained from the model data set.



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Steve Beaver]

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 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 believe neither DCB nor LIKE can be used in nor refer to DD PATH=
> 
> The alternative might be to use JCL symbols for common attribute strings.
> 
> Combining brevity and mnemonic value:
>Q = "'"
>QQ = '"'
> 
> Don't forget to mention them in PROCEDURE EXPOSE.
> SIGNAL ON NOVALUE would remind you, if you chose to use it.
> 
> --
> 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

Re: allowed characters in member name

[Paul Gilmartin]

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 always, no one supplied an RFE with a sufficient use case.

And if they answer Shmuel's FAMS question they have to kill him.
It's absurd that so useful a facility remains a trade secret.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Paul Gilmartin]

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 believe neither DCB nor LIKE can be used in nor refer to DD PATH=

The alternative might be to use JCL symbols for common attribute strings.

Combining brevity and mnemonic value:
Q = "'"
QQ = '"'

Don't forget to mention them in PROCEDURE EXPOSE.
SIGNAL ON NOVALUE would remind you, if you chose to use it.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Phil Smith III]

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.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Seymour J Metz]

Is there a FAMS equivalent to STOW? Does member 8'X'FF' work wit PDSE?

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר


From: IBM Mainframe Discussion List  on behalf of 
Paul Gilmartin <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 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.
STOW 8X'FF'   probably doesn't or produces unexpected results.

--
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

Re: allowed characters in member name

[Paul Gilmartin]

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.
STOW 8X'FF'   probably doesn't or produces unexpected results.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Seymour J Metz]

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://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר


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 +, 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 recall wrong, but I think LIKE was new with SMS.
>
Formerly needed; now deprecated.  Why was it ever needed?  I suspect the change
was less to accommodate SMS than UNIX files, which support attributes but no 
DCB.

Answering my earlier question (IRTFM):

Example 2
//SMSDS7  DD  DSNAME=MYDS7.PGM,LIKE=MYDSCAT.PGM,DISP=(NEW,KEEP),
//  LRECL=1024
In the example, the data set attributes used for MYDS7.PGM are obtained from
the cataloged model data set MYDSCAT.PGM. Also, the logical record length of
1024 overrides the logical record length obtained from the model data set.

--
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

Re: allowed characters in member name

[Phil Smith III]

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 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?


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Wayne Bickerdike]

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 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 recall wrong, but I think LIKE was new with SMS.
> >
> Formerly needed; now deprecated.  Why was it ever needed?  I suspect the
> change
> was less to accommodate SMS than UNIX files, which support attributes but
> no DCB.
>
> Answering my earlier question (IRTFM):
> 
> Example 2
> //SMSDS7  DD  DSNAME=MYDS7.PGM,LIKE=MYDSCAT.PGM,DISP=(NEW,KEEP),
> //  LRECL=1024
> In the example, the data set attributes used for MYDS7.PGM are
> obtained from
> the cataloged model data set MYDSCAT.PGM. Also, the logical record
> length of
> 1024 overrides the logical record length obtained from the model data
> set.
>
> --
> gil
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 
Wayne V. Bickerdike

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Style (was: LISTDSI - ...)

[Wayne Bickerdike]

I often create a function to deal with quotes. Typically I'll use an
UNQUOTE function and a REQUOTE function. My use of the letter Q was by way
of an example.

MyDSN = UNQUOTE(MyDSN)
MyDSN = REQUOTE(MyDSN)

Use of the STRIP function is recommended too. This is where embedded quotes
can confuse:

STRIP(MyDSN,,"'") or
STRIP(MyDSN,,QuoteChar)

I know which I prefer..

On Sun, Jan 7, 2024 at 1:23 PM Paul Gilmartin <
042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:

> On Sun, 7 Jan 2024 01:36:44 +, Seymour J Metz wrote:
>
> >It is a capital error to assume unfamiliarity just because sombody
> eschews a language feature. I am a very heavy user of abuttment in REXX. I
> agree with Wayne that there is a good case for using variables in this
> particular case,
> >
> I agree strongly when a string expression is to be used repeatedly.
> Less so for assigning a single character string to a symbol.
>
> > although I would quarrel with his coice of name. The constructs '"' and
> "'" can be hard to visually distinquisheverywhere they appear. The style
> >
> >apost = "'"
> >uoote = '"'
> >
> (proportional fonts aggravate the problem.)
> >...
> >foo = apost|bar||apost
> >
> A mone mnemonic name (Hungarian notation?) might be:
> fqbar = apost||bar||apost
>
> >concetrrate the problem at the point of definition.
>
> --
> gil
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 
Wayne V. Bickerdike

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Paul Gilmartin]

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 recall wrong, but I think LIKE was new with SMS.
>
Formerly needed; now deprecated.  Why was it ever needed?  I suspect the change
was less to accommodate SMS than UNIX files, which support attributes but no 
DCB.

Answering my earlier question (IRTFM):

Example 2
//SMSDS7  DD  DSNAME=MYDS7.PGM,LIKE=MYDSCAT.PGM,DISP=(NEW,KEEP),
//  LRECL=1024
In the example, the data set attributes used for MYDS7.PGM are obtained from
the cataloged model data set MYDSCAT.PGM. Also, the logical record length of
1024 overrides the logical record length obtained from the model data set.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Gibney, Dave]

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 recall wrong, but I think LIKE was new with SMS.

> -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 +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
>  defense.com%2Fv3%2F__https%3A%2F%2Fwww.ibm.com%2Fdocs%2Fen%
> 2Fzos%2F3.1.0%3Ftopic%3Ddp-syntax-
> 2__%3B!!JmPEgBY0HMszNaDT!t9cNADlF8YggV3ftQnDqq6_pEAAjAFaVbaK2k
> fJgOesh1r7d9dqid5L-
> WIIW1zb5mpfhGtk7tLl2BCULYpCb41cuw0K2G4c3%24=05%7C02%7C
> GIBNEY%40WSU.EDU%7C67f73d32256d4c107e3608dc0fc30cd4%7Cb52be
> 471f7f147b4a8790c799bb53db5%7C0%7C0%7C638402577608244597%7
> CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJ
> BTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=5avD4PTklj
> wHUQOVSoHwar90iho8VQVuCtgOLxfh5gM%3D=0 >:
> [ DCB= ( {dsname   }[,subparameter]...) ]
> 
> Is it possible likewise to override selected subparameters of LIKE?  Was it so
> even before the subparameters were allowed as separare parameters?  (Old
> habits diehard.)
> 
> --
> 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

Re: allowed characters in member name

[Paul Gilmartin]

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 :
[ DCB= ( {dsname   }[,subparameter]...) ]

Is it possible likewise to override selected subparameters
of LIKE?  Was it so even before the subparameters were allowed
as separare parameters?  (Old habits diehard.)

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Paul Gilmartin]

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 for middleware (TSO, JCL, ...) to impose syntactic 
restrictipns
beyond those enforced by the primitives.  Apostrophes should be your friend.


>> On Jan 7, 2024, at 13:55, Radoslaw Skorupka wrote:
>> 
>> 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 whatever is parsing a 
>>> DSN would care whether it's a number or not. E.g.:
>>> //SYSINDD   DISP=SHR,DSN=1.2.3
>>> 
>>> Why would it care that it's a digit? The start of a non-initial DSN element 
>>> is the thing after a period, so it doesn't matter there.
>>> 
The period is not part of the DSN element.  Its a separator.

Perhaps my imaginary lexical analyzer returns numbers in fixed-point format;
other things as strings.

Why is LRECL=080 acceptable but BUFNO=080 a syntax error?

>>> My guess is something planned/considered that never happened, or just a 
>>> mistake late on a Sunday afternoon in 1962.
>> 
Storage was expensive then.

>> The "8 characters rule" is widely used in z/OS and mainframe world.
>> Why?
>> I heard an explanation for that. However it was approx. 25 years ago I did 
>> not fully understand it. Since at the time the rule was enough for me, I 
>> didn't ask. It was something related to assembler, as far as I remember.
>> 
Storage was expensive then.

A UNIX historian recalls an era when directory entries were 16 bytes:
file names were limited to 14 and I-numbers to 65535.

UNIX got better; MVS didn't.  It's the curse of Assembler compatibility
with inadequate parameterization in copybooks.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Radoslaw Skorupka]

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 a reference to define DCB subparameters such as:
 DCB=HLQ.FOO-BAR* Syntax error!


Is there any plausible reason for that restriction

I hate JCL!


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.


--
Radoslaw Skorupka
Lodz, Poland

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Steve Beaver]

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 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 whatever is parsing a DSN 
>> would care whether it's a number or not. E.g.:
>> //SYSINDD   DISP=SHR,DSN=1.2.3
>> 
>> Why would it care that it's a digit? The start of a non-initial DSN element 
>> is the thing after a period, so it doesn't matter there.
>> 
>>  
>> My guess is something planned/considered that never happened, or just a 
>> mistake late on a Sunday afternoon in 1962.
> 
> The "8 characters rule" is widely used in z/OS and mainframe world.
> Why?
> I heard an explanation for that. However it was approx. 25 years ago I did 
> not fully understand it. Since at the time the rule was enough for me, I 
> didn't ask. It was something related to assembler, as far as I remember.
> 
> 
> --
> Radoslaw Skorupka
> Lodz, Poland
> 
> --
> 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

Re: allowed characters in member name

[Radoslaw Skorupka]

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 whatever is parsing a DSN 
would care whether it's a number or not. E.g.:
//SYSINDD   DISP=SHR,DSN=1.2.3

Why would it care that it's a digit? The start of a non-initial DSN element is 
the thing after a period, so it doesn't matter there.

  


My guess is something planned/considered that never happened, or just a mistake 
late on a Sunday afternoon in 1962.


The "8 characters rule" is widely used in z/OS and mainframe world.
Why?
I heard an explanation for that. However it was approx. 25 years ago I 
did not fully understand it. Since at the time the rule was enough for 
me, I didn't ask. It was something related to assembler, as far as I 
remember.



--
Radoslaw Skorupka
Lodz, Poland

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Radoslaw Skorupka]

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 consider uprotected datasets, but IMHO it has no 
practical usage.




--
Radoslaw Skorupka
Lodz, Poland




W dniu 07.01.2024 o 18:15, Michael Oujesky pisze:

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 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., SYS2.PHX-BDT.SJBDMAC), but not in the first.


Since we prefer to deliver product data sets with the product name 
as the first qualifier, we settled on using PHXBDT instead...




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Phil Smith III]

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 number or not. E.g.:
//SYSINDD   DISP=SHR,DSN=1.2.3

Why would it care that it's a digit? The start of a non-initial DSN element is 
the thing after a period, so it doesn't matter there.

 

My guess is something planned/considered that never happened, or just a mistake 
late on a Sunday afternoon in 1962.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: allowed characters in member name

[Michael Oujesky]

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 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., SYS2.PHX-BDT.SJBDMAC), but not in the first.


Since we prefer to deliver product data sets with the product name 
as the first qualifier, we settled on using PHXBDT instead...


--
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