Re: Unable to ALLOC dsn without new
On Fri, 4 Dec 2020 14:38:29 -0800, Ed Jaffe wrote: >On 11/24/2020 8:35 AM, Elaine Beal wrote: >> I thought you had to have the new parm but i can ALLOC a new dsn under >> another id without it. > >New is the default in JCL. Maybe on ALLOC too! > From: z/OS: TSO/E Command Reference (They don't make it easy to remember): If you do not specify OLD, SHR, MOD, NEW, or SYSOUT, a default value is assigned or a value is prompted for, depending on the other operands specified: • If the LIKE operand or any space operands (SPACE, DIR, BLOCK, BLKSIZE, AVBLOCK, TRACKS, or CYLINDERS) are specified, then the status defaults to NEW. • If the COPIES operand is specified, then the status defaults to SYSOUT. • If the DATASET/DSNAME operand is entered without the LIKE operand or any space operands, then the status defaults to OLD. • If the LIKE operand, the DATASET/DSNAME operand, and the space operands are all omitted, you are prompted to enter a status value. In JCL, MOD may not have exactly the desired behavior. Sometimes I've resorted to: //HANDLE DD DISP=(MOD,CATLG),SPACE... //SYSUT2 DD DISP=OLD,DSN=*.HANDLE,VOL=REF=*.HANDLE -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Unable to ALLOC dsn without new
On 11/24/2020 8:35 AM, Elaine Beal wrote: I thought you had to have the new parm but i can ALLOC a new dsn under another id without it. New is the default in JCL. Maybe on ALLOC too! -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Unable to ALLOC dsn without new
A little bit of return code checking from ALLOCATE commands? Mike Wawiorko This e-mail and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments. Internet communications are not guaranteed to be secure or virus-free. The Barclays Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any Internet communications by any third party, or from the transmission of any viruses. Replies to this e-mail may be monitored by the Barclays Group for operational or business reasons. Any opinion or other information in this e-mail or its attachments that does not relate to the business of the Barclays Group is personal to the sender and is not given or endorsed by the Barclays Group. Barclays Execution Services Limited provides support and administrative services across Barclays group. Barclays Execution Services Limited is an appointed representative of Barclays Bank UK plc, Barclays Bank plc and Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays Bank plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority. Clydesdale Financial Services Limited is authorised and regulated by the Financial Conduct Authority. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Unable to ALLOC dsn without new
some thoughts. SYSDSN() use of disp MOD confirm ALIAS exists Use REXX to OUTTRAP the various TSO commands, and analyze the results in code. Regards Bruce -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Unable to ALLOC dsn without new
so... I have looked at every dsn in the logon proc SYSPROC and SYSEXEC i found two places where the 'offending' dataset is being allocated new, including the one that issues the error messages I inserted a CONTROL LIST CONLIST SYMLIST MSG and a listcat and I see no output when logging on to the new userid. ugh -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Unable to ALLOC dsn without new
so now I've got a lead on our good friend SMS :( which of course hasn't changed in 2 years. looks like maybe storclas isn't being defined -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Unable to ALLOC dsn without new
Gil, thanks. I do get that message but when I do a listcat, the mastcat and usercat look correct. They look the same as other previously defined users. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Unable to ALLOC dsn without new
Familiarity?
Operand parsing?
Stack?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Lizette Koehler
Sent: Tuesday, November 24, 2020 1:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Unable to ALLOC dsn without new
I would put a LISTC ENT for the dataset before the allocation
If RC > 0 Then write out some diagnostics
Not sure why people are still writing in CLIST rather than using REXX. But to
each their own
Lizette
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Elaine Beal
Sent: Tuesday, November 24, 2020 9:36 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Unable to ALLOC dsn without new
I give up :), asking for help
Defining a new user and logon proc issues
SET =
ALLOC FI(ISPPROF) SHR DA('')
the dsn is new and evidently the alloc fails
but i can manually alloc a new dsn without the new parm (under another ID)
if I try a manual allocate with the failing ID (and no new parm), it fails with
ALLOC FI(ISPPROF) SHR DA('gayleyc.isptabl')
DATA SET GAYLEYC.ISPTABL NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
ENTER DATA SET NAME -
I thought you had to have the new parm but i can ALLOC a new dsn under another
id without it.
The ALLOC proc works on another LPAR.
Thanks,
Elaine
--
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
Re: Unable to ALLOC dsn without new
On Tue, 24 Nov 2020 10:35:40 -0600, Elaine Beal wrote:
>I give up :), asking for help
>
>Defining a new user and logon proc issues
>
>SET =
>ALLOC FI(ISPPROF) SHR DA('')
>
>the dsn is new and evidently the alloc fails
>
>but i can manually alloc a new dsn without the new parm (under another ID)
>
>if I try a manual allocate with the failing ID (and no new parm), it fails with
>
>ALLOC FI(ISPPROF) SHR DA('gayleyc.isptabl')
> DATA SET GAYLEYC.ISPTABL NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
> ENTER DATA SET NAME -
>
>I thought you had to have the new parm but i can ALLOC a new dsn under another
>id without it.
>
>The ALLOC proc works on another LPAR.
Why are you saying SHR? That indicates that the data set already exists.
If this was in JCL, NEW would be the default if you don't say NEW, OLD, or SHR.
But if you say SHR the data set must already exist. I don't know if TSO will
similarly default to NEW if you omit SHR, but it seems correct for it to
complain if you say SHR when the data set does not exist.
--
Walt
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Unable to ALLOC dsn without new
I would put a LISTC ENT for the dataset before the allocation
If RC > 0 Then write out some diagnostics
Not sure why people are still writing in CLIST rather than using REXX. But to
each their own
Lizette
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Elaine Beal
Sent: Tuesday, November 24, 2020 9:36 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Unable to ALLOC dsn without new
I give up :), asking for help
Defining a new user and logon proc issues
SET =
ALLOC FI(ISPPROF) SHR DA('')
the dsn is new and evidently the alloc fails
but i can manually alloc a new dsn without the new parm (under another ID)
if I try a manual allocate with the failing ID (and no new parm), it fails with
ALLOC FI(ISPPROF) SHR DA('gayleyc.isptabl')
DATA SET GAYLEYC.ISPTABL NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
ENTER DATA SET NAME -
I thought you had to have the new parm but i can ALLOC a new dsn under another
id without it.
The ALLOC proc works on another LPAR.
Thanks,
Elaine
--
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: Unable to ALLOC dsn without new
aarrgghh. sorry about that one too. RACF profiles are created correctly -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Unable to ALLOC dsn without new
What about the relevant security profiles? Was there a security violation logged? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Elaine Beal Sent: Tuesday, November 24, 2020 12:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Unable to ALLOC dsn without new sorry, yes, there is an alias defined -- 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: Unable to ALLOC dsn without new
sorry, yes, there is an alias defined -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Unable to ALLOC dsn without new
First, check whether the userid is an alias to a user catalog. Second, if you
don't already have a dialog for creating a ne user, I recommend that you write
one to automate everything.
It's generally easier to diagnose problems under TSO if you enable all output,
e.g., PROFILE MSGID WTPMSG.; in this case I'm pretty confident that it's a
catalog or security issue.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Elaine Beal
Sent: Tuesday, November 24, 2020 11:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Unable to ALLOC dsn without new
I give up :), asking for help
Defining a new user and logon proc issues
SET =
ALLOC FI(ISPPROF) SHR DA('')
the dsn is new and evidently the alloc fails
but i can manually alloc a new dsn without the new parm (under another ID)
if I try a manual allocate with the failing ID (and no new parm), it fails with
ALLOC FI(ISPPROF) SHR DA('gayleyc.isptabl')
DATA SET GAYLEYC.ISPTABL NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
ENTER DATA SET NAME -
I thought you had to have the new parm but i can ALLOC a new dsn under another
id without it.
The ALLOC proc works on another LPAR.
Thanks,
Elaine
--
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: Unable to ALLOC dsn without new
On Tue, 24 Nov 2020 10:35:40 -0600, Elaine Beal wrote:
>...
>ALLOC FI(ISPPROF) SHR DA('gayleyc.isptabl')
> DATA SET GAYLEYC.ISPTABL NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
> ENTER DATA SET NAME -
>
This is an either/or message of the sort I despise. The code and
text should distinguish between two cases with distinct code and text:
o DATA SET GAYLEYC.ISPTABL NOT IN CATALOG
o CATALOG CAN NOT BE ACCESSED
In either case the message should identify the catalog. If it's MASTER,
that's a big step toward problem determination.
z/OS is far less storage-constrained than when such catch-all messages
were invented. It's past time to fix them.
-- gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Unable to ALLOC dsn without new
On Tue, 24 Nov 2020 10:35:40 -0600, Elaine Beal wrote:
>...
>ALLOC FI(ISPPROF) SHR DA('gayleyc.isptabl')
> DATA SET GAYLEYC.ISPTABL NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
> ENTER DATA SET NAME -
>
Do you need to DEFINE a catalog alias?
SHR? NEW? Whatever.
-- gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Unable to ALLOC dsn without new
I give up :), asking for help
Defining a new user and logon proc issues
SET =
ALLOC FI(ISPPROF) SHR DA('')
the dsn is new and evidently the alloc fails
but i can manually alloc a new dsn without the new parm (under another ID)
if I try a manual allocate with the failing ID (and no new parm), it fails with
ALLOC FI(ISPPROF) SHR DA('gayleyc.isptabl')
DATA SET GAYLEYC.ISPTABL NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
ENTER DATA SET NAME -
I thought you had to have the new parm but i can ALLOC a new dsn under another
id without it.
The ALLOC proc works on another LPAR.
Thanks,
Elaine
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
