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
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
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
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,
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
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
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
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 Discuss
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
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
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
-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
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
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.;
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
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
16 matches
Mail list logo
