Re: ISPF setup macro

2024-01-06 Thread Jon Perryman
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

Re: ISPF setup macro

2024-01-06 Thread Seymour J Metz
Mainframe Discussion List on behalf of Jon Perryman Sent: Saturday, January 6, 2024 3:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ISPF setup macro 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 prob

Re: ISPF setup macro

2024-01-06 Thread Jon Perryman
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

Re: ISPF setup macro

2024-01-05 Thread Willy Jensen
"INRTDDN, which is valid for INFO but not for ALLOC" For alloc you must use the RTDSN(varname) parameter. But a good point, it really should have been the same. -- For IBM-MAIN subscribe / signoff / archive access instructions,

Re: ISPF setup macro

2024-01-05 Thread Seymour J Metz
: ISPF setup macro On Fri, 29 Dec 2023 13:10:27 +, Seymour J Metz wrote: >I'm not trying to setuup an ISPF application environment.; I'm trying to set >up a TSO user environment. TSO user environment limits your options. LIBDEF is not suitable because it is lost or replaced at v

Re: ISPF setup macro

2024-01-05 Thread Seymour J Metz
: Friday, December 29, 2023 12:21 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ISPF setup macro On Fri, 29 Dec 2023 13:10:27 +, Seymour J Metz wrote: >I'm not trying to setuup an ISPF application environment.; I'm trying to set >up a TSO user environment. TSO user environment limits your o

Re: ISPF setup macro

2023-12-29 Thread Jon Perryman
On Fri, 29 Dec 2023 13:10:27 +, Seymour J Metz wrote: >I'm not trying to setuup an ISPF application environment.; I'm trying to set >up a TSO user environment. TSO user environment limits your options. LIBDEF is not suitable because it is lost or replaced at various times. ISPxUSR is not

Re: ISPF setup macro

2023-12-29 Thread Seymour J Metz
Thursday, December 28, 2023 9:55 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ISPF setup macro On Thu, 28 Dec 2023 02:01:54 +, Seymour J Metz wrote: >I'm trying to use LIBDEF as an alternative to freeing and reallocating the >standard ISPF concatenations. LIBDEF is commonly used to eli

Re: ISPF setup macro

2023-12-28 Thread Jon Perryman
On Thu, 28 Dec 2023 02:01:54 +, Seymour J Metz wrote: >I'm trying to use LIBDEF as an alternative to freeing and reallocating the >standard ISPF concatenations. LIBDEF is commonly used to eliminate the need for reallocating standard ISPF DDs. There are situations where ISPxUSR is useful

Re: ISPF setup macro

2023-12-27 Thread Seymour J Metz
-MAIN@LISTSERV.UA.EDU Subject: Re: ISPF setup macro On Wed, 27 Dec 2023 19:59:26 +, Seymour J Metz wrote: What you are asking does not make any sense. >Do the LIBDEFs with DATASET pick up SPPxUSR if there is no ID keyword? I assume SSPxUSR actually means ISPxUSR. I can only comment from w

Re: ISPF setup macro

2023-12-27 Thread Jon Perryman
On Wed, 27 Dec 2023 19:59:26 +, Seymour J Metz wrote: What you are asking does not make any sense. >Do the LIBDEFs with DATASET pick up SPPxUSR if there is no ID keyword? I assume SSPxUSR actually means ISPxUSR. I can only comment from what I've read because ISPxUSR does not solve my

ISPF setup macro

2023-12-27 Thread Seymour J Metz
I want to write a REXX script to initialize an ISPF session, assuming that another script has already allocated the necessary user data sets and issue TSOLIB. Tentatively I assume that I need address TSO ALTLIB ACTIVATE 'USER(EXEC)' address ISPEXEC LIBDEF ISPPLIB DATASET address