GDS?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
From: IBM Mainframe Discussion List on behalf of
Phil Smith III
Sent: Saturday, January 6, 2024 9:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
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
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
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
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,
although I would quarrel with his coice of name. The constructs
Sorry, right reply to wrong message.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
From: IBM Mainframe Discussion List on behalf of
Seymour J Metz
Sent: Saturday, January 6, 2024 7:40 PM
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 Sun, 7 Jan 2024 00:31:30 +, Seymour J Metz wrote:
>ALLOC DSN(userid.USER.ISPM) INRTDNN(MYDD) SHR
>
>So why -24 instead of -23?
>
>Changing the *3rd* key to RTDDN fixed the problem.
The word KEY is ambiguous and may not mean KEYWORD.
Total guess but considering this syntax is not
The issue goes beyond what remedies are available. An open source project
depends upon voluntary contributors. If potential contributors don't trust you
to obey license term, you risk being abandoned.
OTOH, changing the license, asking each contributor for permission and removing
the code from
The manual says:
-21 to -
Key error. See “Key errors” on page 204 for more information.
and
The low-order two digits are the number of the key that failed the parse,
offset by 20. The first key has the value 21,
resulting in a return code of -21.
The parameter was
> I think that he's not getting a "flooding" condition at all, he probably just
> hit enter on his emulator,
> IEE163I MODE= HELD IEE159E MESSAGE WAITING
The OP showed the IEE163I which showed MODE=RD with the IEE159E. It's possible
he intentionally used hold mode and caused the message
On Thu, 4 Jan 2024 18:16:49 +0100, Radoslaw Skorupka
wrote:
>Sometimes I observe IXG251I and IXG284I
>ISG251I informs the dataset is in use by another sysplex member
>IXG284I says the dataset is PENDING DELETE.
Use the DISPLAY LOGGER CONNECTIONS command to see if something unexpected is
On Thu, 4 Jan 2024 12:31:36 -0600, Paul Gorlinsky
wrote:
>On a z/OS 2.5 system using z System Automation V4.3, >
>The event needs to issue a 'W L' then locate the SYSLOG output for that
>specific LPAR,
There are many ways to solve this problem and various considerations.
>Where STC08984 is
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
You can see such member names in SMP dataset and CA PDSMAN managed
datasets.
However this is NOT what I'm talking about.
I mean "regular" member names used in JCL and/or in ISPF dialogs.
BTW: it is NOT "regular character set" understood as A-Z, 0-9, #$@ with
no numeric on first position. It is
On Fri, 5 Jan 2024 08:10:52 -0600, Willy Jensen
wrote:
>When running in Netview it doesn't abend, but it doesn't do anything either,
> except that the return value is valid. It returns 0, which indicates success.
Saying "returns 0" tells us nothing.
>The function in question reads. lists and
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
Way to miss the point.
On Sun, Jan 7, 2024 at 2:58 AM Paul Gilmartin <
042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:
> On Sat, 6 Jan 2024 14:25:09 +1100, Wayne Bickerdike wrote:
>
> >Quoted strings always gave me grief. I started to use Q='7D'X and
> >concatenate my strings this way:
>
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
On Fri, 5 Jan 2024 17:41:45 +, Seymour J Metz wrote:
>I've been using BPXWDYN for allocation and concatenation, but I had a problem
>with an error code -24.
UNIX standards provide error codes versus z/OS typically provide an error code
and error message. There's a learning curve for
On Sat, 6 Jan 2024 04:06:59 -0600, Willy Jensen
wrote:
>"PROF NOPREFIX works but can leave you that setting when you don't want it on
>termination."
PROF NOPREFIX should never be used especially if you can't figure out quoting.
You are potentially creating problems for others working on your
On Sat, 6 Jan 2024 14:25:09 +1100, Wayne Bickerdike wrote:
>Quoted strings always gave me grief. I started to use Q='7D'X and
>concatenate my strings this way:
>
>Str = Q||DsNAme||Q.
>LISTDSI(Str)
>
I find that less transparent and surely more verbose than:
LISTDSI( "'"DsNAme"'" ) or even:
"PROF NOPREFIX works but can leave you that setting when you don't want it on
termination."
Do check if it is already off before you change it, and if so dont set it on
afterwards. Also remember that the prefix is not neccessarily the user id, so
you need something like the following to
26 matches
Mail list logo
