Re: AutoIPL

[Tom Brennan]

The only problem I remember was a Dev system early morning auto IPL that 
we didn't even notice until maybe a day later.  I think after that we 
started a task at IPL time that sent us an email.


On 1/10/2025 11:05 AM, David Purdy wrote:

  The only problem with Autoipl is if an LPAR abends, it keeps on IPLing until 
operations or automated process notices
Happened once in five years
David
 On Friday, January 10, 2025 at 01:33:15 PM EST, Steve Beaver 
<050e0c375a14-dmarc-requ...@listserv.ua.edu> wrote:
  
  I'm new to the USDOJ and my lead put in an IPL request for the sandbox - No big deal.


Well the operators got the system down and then auto magically the system
Started coming up and I asked how??

In a no changes environment as that IPL was - it was quick - No HMC to 
manipulate





-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Allan Staller
Sent: Friday, January 10, 2025 12:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AutoIPL

Classification: Confidential

Discovered...Yes used (never)

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Steve Beaver
Sent: Friday, January 10, 2025 12:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AutoIPL

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

How many of you have discovered the Auto IPL feature for zOS


Steve

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

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.


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




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

Re: AutoIPL

[Radoslaw Skorupka]

I think there is some misunderstanding.
I started using it long time ago.
Last time I used it yesterday.
BTW: I created ad-hoc DIAGxx member to IPL from different sysres device, 
new OS level.


BTW2: Loong (even longer) time ago I was the first person in a shop 
who logged on to HMC remotely, from my desktop.
After our office was moved and walk to HMC took few minutes colleagues 
asked me how to logon remotely. :-)


--
Radoslaw Skorupka
Lodz, Poland




W dniu 10.01.2025 o 20:33, Steve Beaver pisze:

I have a friend that will not use AutoIPL for God , love , or money




This electronic mail (including any attachments) may contain information that 
is privileged, confidential, and/or otherwise protected from disclosure to 
anyone other than its intended recipient(s). Any dissemination or use of this 
electronic email or its contents (including any attachments) by persons other 
than the intended recipient(s) is strictly prohibited. If you have received 
this message in error, please notify us immediately by reply email so that we 
may correct our internal records. Please then delete the original message 
(including any attachments) in its entirety. Thank you


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Radoslaw Skorupka
Sent: Friday, January 10, 2025 1:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AutoIPL

W dniu 10.01.2025 o 19:12, Steve Beaver pisze:

How many of you have discovered the Auto IPL feature for zOS

Me.
However it was looong time ago. 2016, or rather earlier.



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

Re: AutoIPL

[Albertus de Wet]

I would also like to do this. Any chance you can share the parms in DIAGxx
that are needed for this?
I tried it a while back, but must have missed something, obvious, obviously.

On Fri, Jan 10, 2025 at 2:42 PM Radoslaw Skorupka <
0471ebeac275-dmarc-requ...@listserv.ua.edu> wrote:

> I think there is some misunderstanding.
> I started using it long time ago.
> Last time I used it yesterday.
> BTW: I created ad-hoc DIAGxx member to IPL from different sysres device,
> new OS level.
>
> BTW2: Loong (even longer) time ago I was the first person in a shop
> who logged on to HMC remotely, from my desktop.
> After our office was moved and walk to HMC took few minutes colleagues
> asked me how to logon remotely. :-)
>
> --
> Radoslaw Skorupka
> Lodz, Poland
>
>
>
>
> W dniu 10.01.2025 o 20:33, Steve Beaver pisze:
> > I have a friend that will not use AutoIPL for God , love , or money
> >
> >
> >
> 
> >
> > This electronic mail (including any attachments) may contain information
> that is privileged, confidential, and/or otherwise protected from
> disclosure to anyone other than its intended recipient(s). Any
> dissemination or use of this electronic email or its contents (including
> any attachments) by persons other than the intended recipient(s) is
> strictly prohibited. If you have received this message in error, please
> notify us immediately by reply email so that we may correct our internal
> records. Please then delete the original message (including any
> attachments) in its entirety. Thank you
> >
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Radoslaw Skorupka
> > Sent: Friday, January 10, 2025 1:15 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: AutoIPL
> >
> > W dniu 10.01.2025 o 19:12, Steve Beaver pisze:
> >> How many of you have discovered the Auto IPL feature for zOS
> > Me.
> > However it was looong time ago. 2016, or rather earlier.
> >
>
> --
> 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: Bye all

[David Crayford]

The large insurance company in my town switched the lights off in the mainframe 
last month. We’re now down to 1 remaining mainframe site, a bank. When I moved 
here 26 years ago there were about 15 sites. I can remember the carnage of the 
90s when jumping to SAP was the thing. And contrary to the fluff pieces on the 
PlanetMainframe site those migrations did not fail. 

> On 10 Jan 2025, at 22:43, Steve Beaver 
> <050e0c375a14-dmarc-requ...@listserv.ua.edu> wrote:
> 
> I had a customer, a mid-sized insurance company that stated in 1995 they 
> were exiting 
> The mainframe space.  Well its 2025 and they are still on a z13
> 
> 
> 
> 
> 
> 
> 
> This electronic mail (including any attachments) may contain information that 
> is privileged, confidential, and/or otherwise protected from disclosure to 
> anyone other than its intended recipient(s). Any dissemination or use of this 
> electronic email or its contents (including any attachments) by persons other 
> than the intended recipient(s) is strictly prohibited. If you have received 
> this message in error, please notify us immediately by reply email so that we 
> may correct our internal records. Please then delete the original message 
> (including any attachments) in its entirety. Thank you
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Mike Schwab
> Sent: Friday, January 10, 2025 12:40 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Bye all
> 
> https://planetmainframe.com/2023/06/sabre-is-getting-off-the-mainframe-one-way-or-another/
> 
>> On Thu, Jan 9, 2025 at 11:14 PM The North American Becker
>> <0762a73125b7-dmarc-requ...@listserv.ua.edu> wrote:
>> 
>> The mainframe is dead.
>> 
>> --
>> 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
> 
> --
> 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: Bye all

[Charles Mills]

Let me start by saying nobody loves the mainframe more than I do. The 
mainframe, and the mainframe software business, has been very, very good to me.

That said, no matter how many times we tell smirking tales here of someone's 
get-off-the-mainframe project that failed or took three times as long as 
expected, the fact is that this is a platform that it would seem that perhaps 
three out of four installations *wish* they were off of. That is not something 
that makes me proud, and I don't think it should make any of us proud. If I 
were a senior executive at IBM, it would not make me proud, and in fact would 
be a severe danger warning. The fact that there is no magic 
get-off-the-mainframe solution today does not mean that there will not be one 
tomorrow.

Charles


On Sat, 11 Jan 2025 06:05:49 +0800, David Crayford  wrote:

>The large insurance company in my town switched the lights off in the 
>mainframe last month. We’re now down to 1 remaining mainframe site, a bank. 
>When I moved here 26 years ago there were about 15 sites. I can remember the 
>carnage of the 90s when jumping to SAP was the thing. And contrary to the 
>fluff pieces on the PlanetMainframe site those migrations did not fail. 
>
>> On 10 Jan 2025, at 22:43, Steve Beaver 
>> <050e0c375a14-dmarc-requ...@listserv.ua.edu> wrote:
>> 
>> I had a customer, a mid-sized insurance company that stated in 1995 they 
>> were exiting 
>> The mainframe space.  Well its 2025 and they are still on a z13

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

Re: Canonical way to limit a concatenated tape file DD to two tape drives?

[Michael Oujesky]

See UNIT=AFF

At 06:02 PM 1/10/2025, Farley, Peter wrote:
I have a business need to scan 15 different tape files (all the same 
record format, some are multi-volume) to extract relevant 
information, and I first tried to scan them all in one concatenated 
DD.  I didn't specify anything but DISP and DSN for each file in the 
concatenation, so I got 15 tape mounts to 15 different tape drives.


I would like to limit the tape drive usage so as not to 
unintentionally interfere with production work that actually needs a 
tape drive.  Using UNIT=AFF=INPUTDD on the second and all other DD's 
in the concatenation limits usage to ONE tape drive, the one 
allocated to the first file in the concatenation.


In order to reduce elapsed time for the scan job (each tape 
dismount/mount operation takes an appreciable amount of time, 
usually at least a minute or so), is there any way to use TWO drives 
in one concatenated DD instead of one drive, so that as each file 
reaches EOF the process continues with the already-mounted next file 
while the system loads the EOF drive with the next file?  If I knew 
in advance the device numbers of tape drives that are actually 
available I could try to use UNIT=device1 and UNIT=device2 on 
alternating DD's, adding ",,DEFER" to all but the first two DD's, 
but I don't know what drives are available before I submit the job.


If there is a way to use two drives without knowing the device 
numbers ahead of time, what happens if one of the tape DD's is a 
file that has multiple volumes?  Does an already-mounted file from 
the next DD get dismounted to load the next volume of the one being 
processed, or does it dismount the first volume and wait for the 
next volume to be mounted on the same drive?


These aren't "real" drives of course, they are all in a VTL, but the 
principal is the same - don't occupy more devices than you really need.


Peter

This message and any attachments are intended only for the use of 
the addressee and may contain information that is privileged and 
confidential. If the reader of the message is not the intended 
recipient or an authorized representative of the intended recipient, 
you are hereby notified that any dissemination of this communication 
is strictly prohibited. If you have received this communication in 
error, please notify us immediately by e-mail and delete the message 
and any attachments from your system.


--
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: Bye all

[Jay Maynard]

I'll note here that my current employer has been in a get-off-the-mainframe
posture for years and only a few months ago officially abandoned that
because there's just too much institutional knowledge that is encapsulated
in it.

On Fri, Jan 10, 2025 at 6:29 PM Charles Mills  wrote:

> Let me start by saying nobody loves the mainframe more than I do. The
> mainframe, and the mainframe software business, has been very, very good to
> me.
>
> That said, no matter how many times we tell smirking tales here of
> someone's get-off-the-mainframe project that failed or took three times as
> long as expected, the fact is that this is a platform that it would seem
> that perhaps three out of four installations *wish* they were off of. That
> is not something that makes me proud, and I don't think it should make any
> of us proud. If I were a senior executive at IBM, it would not make me
> proud, and in fact would be a severe danger warning. The fact that there is
> no magic get-off-the-mainframe solution today does not mean that there will
> not be one tomorrow.
>
> Charles
>
>
> On Sat, 11 Jan 2025 06:05:49 +0800, David Crayford 
> wrote:
>
> >The large insurance company in my town switched the lights off in the
> mainframe last month. We’re now down to 1 remaining mainframe site, a bank.
> When I moved here 26 years ago there were about 15 sites. I can remember
> the carnage of the 90s when jumping to SAP was the thing. And contrary to
> the fluff pieces on the PlanetMainframe site those migrations did not fail.
> >
> >> On 10 Jan 2025, at 22:43, Steve Beaver <
> 050e0c375a14-dmarc-requ...@listserv.ua.edu> wrote:
> >>
> >> I had a customer, a mid-sized insurance company that stated in 1995
> they were exiting
> >> The mainframe space.  Well its 2025 and they are still on a z13
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 
Jay Maynard

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

Re: ISREDIT CAPS ON OFF

[Bob Bridges]

Yeah, I've a REXX exec named SAYNR that does the same thing - passes a string 
to a CLIST that just does a WRITENR with the string.  Nice, but it's not like I 
use it very often - not, indeed, as though it's really even necessary.

---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313

/* While mathematicians often do not have much humility, we all have lots of 
experience with humiliation.  -Dan Goldston, in his acceptance speech for the 
prestigious Cole Prize */

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
David Spiegel
Sent: Thursday, January 9, 2025 19:26

I also have an Exec which calls my Writenr clist.. My point was counter the 
idea that with Rexx, CLISTs are never necessary.

--- On 2025-01-09 19:18, Bill Hitefield wrote:
> I wrote a dinky CLIST to issue WRITENR. I call it from REXX as needed.

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

Re: Canonical way to limit a concatenated tape file DD to two tape drives?

[Mike Schwab]

https://www.ibm.com/docs/en/zos/2.4.0?topic=up-syntax-1

//ddname DD DISP=SHR,DSN=hlq.data.set.name1.llq,
// UNIT=(tape,2)  * device,count
// DD DISP=SHR,DSN=hlq.data.set.name2.llq,
// UNIT=AFF=ddname   * repeat as needed

On Fri, Jan 10, 2025 at 6:02 PM Farley, Peter
<031df298a9da-dmarc-requ...@listserv.ua.edu> wrote:
>
> I have a business need to scan 15 different tape files (all the same record 
> format, some are multi-volume) to extract relevant information, and I first 
> tried to scan them all in one concatenated DD.  I didn't specify anything but 
> DISP and DSN for each file in the concatenation, so I got 15 tape mounts to 
> 15 different tape drives.
>
> I would like to limit the tape drive usage so as not to unintentionally 
> interfere with production work that actually needs a tape drive.  Using 
> UNIT=AFF=INPUTDD on the second and all other DD's in the concatenation limits 
> usage to ONE tape drive, the one allocated to the first file in the 
> concatenation.
>
> In order to reduce elapsed time for the scan job (each tape dismount/mount 
> operation takes an appreciable amount of time, usually at least a minute or 
> so), is there any way to use TWO drives in one concatenated DD instead of one 
> drive, so that as each file reaches EOF the process continues with the 
> already-mounted next file while the system loads the EOF drive with the next 
> file?  If I knew in advance the device numbers of tape drives that are 
> actually available I could try to use UNIT=device1 and UNIT=device2 on 
> alternating DD's, adding ",,DEFER" to all but the first two DD's, but I don't 
> know what drives are available before I submit the job.
>
> If there is a way to use two drives without knowing the device numbers ahead 
> of time, what happens if one of the tape DD's is a file that has multiple 
> volumes?  Does an already-mounted file from the next DD get dismounted to 
> load the next volume of the one being processed, or does it dismount the 
> first volume and wait for the next volume to be mounted on the same drive?
>
> These aren't "real" drives of course, they are all in a VTL, but the 
> principal is the same - don't occupy more devices than you really need.
>
> Peter
>
> This message and any attachments are intended only for the use of the 
> addressee and may contain information that is privileged and confidential. If 
> the reader of the message is not the intended recipient or an authorized 
> representative of the intended recipient, you are hereby notified that any 
> dissemination of this communication is strictly prohibited. If you have 
> received this communication in error, please notify us immediately by e-mail 
> and delete the message and any attachments from your system.
>
> --
> 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: ISREDIT CAPS ON OFF

[Rupert Reynolds]

The one thing I missed from CLIST was the ability to run a CLIST under
TEST, issue TEST commands from that CLIST, and process the output from
them. Everything else I did with Rexx, or compiled code.

Roops

That's a bit of a niche, maybe, when there are better debuggers, but it was
the only way to make progress at one company.

On Fri, 10 Jan 2025, 21:14 Bill Hitefield, 
wrote:

> David,
>
> Understood. I use REXX extensively for ISPF edit macros and such. I was
> agreeing that there were some "nice to have things" which clist did have.
> When I started, clist was the only way to go. Once we were introduced to
> REXX, I began converting clists to EXECs, and found WRITENR was a "clist
> only" entity. I agree with others in that the clist "PROC" could have been
> useful in REXX. I suspect most of us have written some sort of
> general-purpose parsing logic for use in REXX.
>
> At this point, I have only a handful of clists which are still in use.
> Most are "1 time only" type things and are not worth converting.
>
> Bill Hitefield
> Dino-Software Corporation
> 800.480.DINO
> www.dino-software.com
>
> > -Original Message-
> > From: IBM Mainframe Discussion List  On
> > Behalf Of David Spiegel
> > Sent: Thursday, January 9, 2025 7:26 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: ISREDIT CAPS ON OFF
> >
> > Hi Bill,
> > I also have an Exec which calls my Writenr clist.. My point was counter
> the
> > idea that with Rexx, CLISTs are never necessary.
> >
> > Regards,
> > David
> >
> > On 2025-01-09 19:18, Bill Hitefield wrote:
> > > I wrote a dinky CLIST to issue WRITENR. I call it from REXX as needed.
> > >
> > > Bill Hitefield
> > >
> > >> -Original Message-
> > >> From: IBM Mainframe Discussion List  On
> > >> Behalf Of David Spiegel
> > >> Sent: Thursday, January 9, 2025 5:42 PM
> > >> To: IBM-MAIN@LISTSERV.UA.EDU
> > >> Subject: Re: ISREDIT CAPS ON OFF
> > >>
> > >> Hi Tony,
> > >> CLISTs also have the WRITENR statement, which Rexx lacks.
> > >>
> > >> Regards,.
> > >> David
> > >>
> > >> On 2025-01-09 16:49, Tony Harminc wrote:
> > >>> On Wed, 8 Jan 2025 at 19:51, Lennie Bradshaw
> > >>> 
> > >>> wrote:
> > >>>
> >  CLIST design is over 50 years old I think.
> > 
> > >>> CLISTs as we know them arrived with OS VS/2 Release 3, so the second
> > >>> release of MVS around 1974 or so. Before that, on e.g MVT, SVS, and
> > >>> the first MVS, CLISTs had no control flow statements - they were
> > >>> just lists of commands with some substitution for arguments.
> > >>>
> > >>> At introduction, everyone was all excited at the shiny new CLISTs,
> > >>> and I remember well wondering why there was no lower case support,
> > >>> and if it could be easily fixed. Indeed it could, and I found and
> > >>> happily zapped out the upcasing and tried a CLIST with some lower
> > >>> case text in it. It blew up all over the place, and I discovered
> > >>> that pretty much all byte values beyond the upper case letters,
> > >>> numbers, and a few more (i.e. roughly the JCL character set at the
> > >>> time) was being used as internal syntactic markers for various
> > >>> aspects of the language. So much for
> > >> that quick fix.
> > >>> No, I don't remember the details, but I imagine much of today's
> > >>> CLIST processor is unchanged from the 1970s version, and the source
> > >>> code for that is available if anyone wants to research it further.
> > >>>
> > >>> But seriously, why does anyone use CLISTs today? There is to my
> > >>> knowledge just one reason: there is tight integration with TSO
> > >>> parsing and the CLIST header, whereas REXX requires that the command
> > >>> be treated as a single string, and then parsed with the (unarguably
> > >>> powerful)
> > >> REXX parsing scheme.
> > >>> But that doesn't allow for a syntax error to be discovered in the
> > >>> REXX and the user prompted using TSO facilities; the REXX has to do
> > >>> all the work itself.
> > >>>
> > >>> Tony H.
> > >>>
> > >>> 
> > >>> -- 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
> >
> > --
> > 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 /

Canonical way to limit a concatenated tape file DD to two tape drives?

[Farley, Peter]

I have a business need to scan 15 different tape files (all the same record 
format, some are multi-volume) to extract relevant information, and I first 
tried to scan them all in one concatenated DD.  I didn't specify anything but 
DISP and DSN for each file in the concatenation, so I got 15 tape mounts to 15 
different tape drives.

I would like to limit the tape drive usage so as not to unintentionally 
interfere with production work that actually needs a tape drive.  Using 
UNIT=AFF=INPUTDD on the second and all other DD's in the concatenation limits 
usage to ONE tape drive, the one allocated to the first file in the 
concatenation.

In order to reduce elapsed time for the scan job (each tape dismount/mount 
operation takes an appreciable amount of time, usually at least a minute or 
so), is there any way to use TWO drives in one concatenated DD instead of one 
drive, so that as each file reaches EOF the process continues with the 
already-mounted next file while the system loads the EOF drive with the next 
file?  If I knew in advance the device numbers of tape drives that are actually 
available I could try to use UNIT=device1 and UNIT=device2 on alternating DD's, 
adding ",,DEFER" to all but the first two DD's, but I don't know what drives 
are available before I submit the job.

If there is a way to use two drives without knowing the device numbers ahead of 
time, what happens if one of the tape DD's is a file that has multiple volumes? 
 Does an already-mounted file from the next DD get dismounted to load the next 
volume of the one being processed, or does it dismount the first volume and 
wait for the next volume to be mounted on the same drive?

These aren't "real" drives of course, they are all in a VTL, but the principal 
is the same - don't occupy more devices than you really need.

Peter

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

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

Re: ISREDIT CAPS ON OFF

[Seymour J Metz]

Another reason to pick up ooRexx.

BTW, TSO/E REXX does support stream I/O, but only for Eunix files.

--
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: Thursday, January 9, 2025 6:19 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ISREDIT CAPS ON OFF

External Message: Use Caution


On Thu, 9 Jan 2025 17:42:27 -0500, David Spiegelwrote:

>Hi Tony,
>CLISTs also have the WRITENR statement, which Rexx lacks.
>


It's ANSI.  Why does IBM spurn standards‽

From Cowlishaw.  Also in compiled REXX and, lately, in CMS REXX.

--
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: [EXTERNAL] ISPF Edit of same named files

[Pommier, Rex]

Rename one of them temporarily?

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
roscoe5
Sent: Friday, January 10, 2025 8:32 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] ISPF Edit of same named files

I want to Edit a pair of files, from Prod and Test LPARs, both named 
SYS1.TCPPARMS(PROFILE8), concurrently.
I’m trying to make them as consistent as possible, with a lot of minor changes 
to each.
I have them both up in split screen (used their unique VOLSER) but I can only 
have one or the other in Edit at a time, while the other is in View.

Maybe there isn’t a way to do this, but if there is it would make things easier.

Thanks in advance!

Sent from [Proton 
Mail](https://urldefense.com/v3/__https://proton.me/mail/home__;!!KjMRP1Ixj6eLE0Fj!tLbv01a1C0WxpfHK6QmV8nvz-Z9JGIJiUY4fdGopMpWGtuWcn1s3jYdzTaa4g5uFWK1u3IAZkPPIDNBbBHfsNGYO5GOcQ8VSKV2x$
 ) for iOS

--
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: ISPF Edit of same named files

[Mike Schwab]

Try use the VOLSER field.
ISPF 3 has various ways to compare two files to show the difference.

On Fri, Jan 10, 2025 at 8:32 AM roscoe5
<056b62686b81-dmarc-requ...@listserv.ua.edu> wrote:
>
> I want to Edit a pair of files, from Prod and Test LPARs, both named 
> SYS1.TCPPARMS(PROFILE8), concurrently.
> I’m trying to make them as consistent as possible, with a lot of minor 
> changes to each.
> I have them both up in split screen (used their unique VOLSER) but I can only 
> have one or the other in Edit at a time, while the other is in View.
>
> Maybe there isn’t a way to do this, but if there is it would make things 
> easier.
>
> Thanks in advance!
>
> Sent from [Proton Mail](https://proton.me/mail/home) for iOS
>
> --
> 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

ISPF Edit of same named files

[roscoe5]

I want to Edit a pair of files, from Prod and Test LPARs, both named 
SYS1.TCPPARMS(PROFILE8), concurrently.
I’m trying to make them as consistent as possible, with a lot of minor changes 
to each.
I have them both up in split screen (used their unique VOLSER) but I can only 
have one or the other in Edit at a time, while the other is in View.

Maybe there isn’t a way to do this, but if there is it would make things easier.

Thanks in advance!

Sent from [Proton Mail](https://proton.me/mail/home) for iOS

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

Re: ISPF Edit of same named files

[Lionel B Dyck]

use library services to do it

1. allocate each to a unique DD
2. use lminit on each dd
3. edit each using dataid
4. lmfree each when done
5. tso free each dd

rough sample

Address ISPExec
'lminit dataid(ddb) ddname('ddn')'
'Edit dataid('ddb')'
'lmfree dataid('ddb')'
Address TSO,
  'Free f('ddn')'


On Fri, Jan 10, 2025 at 8:32 AM roscoe5
<056b62686b81-dmarc-requ...@listserv.ua.edu> wrote:
>
> I want to Edit a pair of files, from Prod and Test LPARs, both named 
> SYS1.TCPPARMS(PROFILE8), concurrently.
> I’m trying to make them as consistent as possible, with a lot of minor 
> changes to each.
> I have them both up in split screen (used their unique VOLSER) but I can only 
> have one or the other in Edit at a time, while the other is in View.
>
> Maybe there isn’t a way to do this, but if there is it would make things 
> easier.
>
> Thanks in advance!
>
> Sent from [Proton Mail](https://proton.me/mail/home) for iOS
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Lionel B. Dyck <><
Website:https://github.com/lbdyck

"Worry more about your character than your reputation.  Character is
what you are, reputation merely what others think you are." - John
Wooden

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

Re: [EXTERNAL] ISPF Edit of same named files

[roscoe5]

Yep, that would work!
Simple solution, maybe more coffee, too.
I take it that what I was trying is indeed not allowed, and I wonder why not, 
but case closed.
Thanks!

Sent from [Proton Mail](https://proton.me/mail/home) for iOS

On Fri, Jan 10, 2025 at 9:35 AM, Pommier, Rex 
<[0737643a508d-dmarc-requ...@listserv.ua.edu](mailto:On Fri, Jan 10, 2025 
at 9:35 AM, Pommier, Rex < wrote:

> Rename one of them temporarily?
>
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> roscoe5
> Sent: Friday, January 10, 2025 8:32 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] ISPF Edit of same named files
>
> I want to Edit a pair of files, from Prod and Test LPARs, both named 
> SYS1.TCPPARMS(PROFILE8), concurrently.
> I’m trying to make them as consistent as possible, with a lot of minor 
> changes to each.
> I have them both up in split screen (used their unique VOLSER) but I can only 
> have one or the other in Edit at a time, while the other is in View.
>
> Maybe there isn’t a way to do this, but if there is it would make things 
> easier.
>
> Thanks in advance!
>
> Sent from [Proton 
> Mail](https://urldefense.com/v3/__https://proton.me/mail/home__;!!KjMRP1Ixj6eLE0Fj!tLbv01a1C0WxpfHK6QmV8nvz-Z9JGIJiUY4fdGopMpWGtuWcn1s3jYdzTaa4g5uFWK1u3IAZkPPIDNBbBHfsNGYO5GOcQ8VSKV2x$
>  ) for iOS
>
> --
> 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: Bye all

[Steve Beaver]

I had a customer, a mid-sized insurance company that stated in 1995 they were 
exiting 
The mainframe space.  Well its 2025 and they are still on a z13







This electronic mail (including any attachments) may contain information that 
is privileged, confidential, and/or otherwise protected from disclosure to 
anyone other than its intended recipient(s). Any dissemination or use of this 
electronic email or its contents (including any attachments) by persons other 
than the intended recipient(s) is strictly prohibited. If you have received 
this message in error, please notify us immediately by reply email so that we 
may correct our internal records. Please then delete the original message 
(including any attachments) in its entirety. Thank you

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mike Schwab
Sent: Friday, January 10, 2025 12:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Bye all

https://planetmainframe.com/2023/06/sabre-is-getting-off-the-mainframe-one-way-or-another/

On Thu, Jan 9, 2025 at 11:14 PM The North American Becker
<0762a73125b7-dmarc-requ...@listserv.ua.edu> wrote:
>
> The mainframe is dead.
>
> --
> 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

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

Re: ISREDIT CAPS ON OFF

[Seymour J Metz]

I'd probably write a subroutine to parse and expand it, bt it does seem to be a 
PITA.

So we have
DATA
DATA PROMPT
Expressions from external sources
PROC
WRITENR

Anything else?

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




From: IBM Mainframe Discussion List  on behalf of 
Schmitt, Michael 
Sent: Thursday, January 9, 2025 6:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ISREDIT CAPS ON OFF

External Message: Use Caution


One reason to use CLIST is that part of the application is dependent on 
evaluation of CLIST expressions that are stored in a database.

That is, there's some code that dynamically builds expressions in CLIST syntax, 
perhaps decades ago. These expression are in an ISPF table.

Then the later CLIST reads these and uses them. Obviously, using CLIST to get 
values from CLIST expressions is easier than trying to have REXX code parse the 
expression.


...one more obstacle I ran into in re-writing the development system into 4,567 
lines of perfectly structured REXX code.

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Thursday, January 9, 2025 4:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ISREDIT CAPS ON OFF

The only reasons that I can think of to use CLIST is if you need one of

DATA
DATA PROMPT
PROC

Everything else, IMHO, is easier with REXX.

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




From: IBM Mainframe Discussion List  on behalf of 
Tony Harminc 
Sent: Thursday, January 9, 2025 4:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ISREDIT CAPS ON OFF

External Message: Use Caution


On Wed, 8 Jan 2025 at 19:51, Lennie Bradshaw 
wrote:

> CLIST design is over 50 years old I think.
>

CLISTs as we know them arrived with OS VS/2 Release 3, so the second
release of MVS around 1974 or so. Before that, on e.g MVT, SVS, and the
first MVS, CLISTs had no control flow statements - they were just lists of
commands with some substitution for arguments.

At introduction, everyone was all excited at the shiny new CLISTs, and I
remember well wondering why there was no lower case support, and if it
could be easily fixed. Indeed it could, and I found and happily zapped out
the upcasing and tried a CLIST with some lower case text in it. It blew up
all over the place, and I discovered that pretty much all byte values
beyond the upper case letters, numbers, and a few more (i.e. roughly the
JCL character set at the time) was being used as internal syntactic markers
for various aspects of the language. So much for that quick fix.

No, I don't remember the details, but I imagine much of today's CLIST
processor is unchanged from the 1970s version, and the source code for that
is available if anyone wants to research it further.

But seriously, why does anyone use CLISTs today? There is to my knowledge
just one reason: there is tight integration with TSO parsing and the CLIST
header, whereas REXX requires that the command be treated as a single
string, and then parsed with the (unarguably powerful) REXX parsing scheme.
But that doesn't allow for a syntax error to be discovered in the REXX and
the user prompted using TSO facilities; the REXX has to do all the work
itself.

Tony H.

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


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

Re: ISREDIT CAPS ON OFF

[Alan Altmark]

On Thu, 9 Jan 2025 17:19:06 -0600, Paul Gilmartin  wrote:
>
>
>It's ANSI.  Why does IBM spurn standards‽
>
>From Cowlishaw.  Also in compiled REXX and, lately, in CMS REXX.

Only if you define "lately" to mean "over 30 years ago".  Stream I/O was added 
to CMS REXX around 1992.

Alan Altmark
z/VM Development
IBM

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

Re: ISPF Edit of same named files

[Schmitt, Michael]

How does this work? I'm thinking the OP's issue is that the SPFEDIT enqueue's 
minor name is the library and member name, no volser. So even though they are 
two different libraries, the enqueue blocks the 2nd edit.

In my testing, you get the same SPFEDIT enqueue when use edit using a LMINIT 
dataid. Which it would have to, because otherwise they're be a lot of PDS 
corruption caused by simultaneous updates being allowed when one or more Edit 
sessions are via a dialog.


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Lionel B Dyck
Sent: Friday, January 10, 2025 8:37 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ISPF Edit of same named files

use library services to do it

1. allocate each to a unique DD
2. use lminit on each dd
3. edit each using dataid
4. lmfree each when done
5. tso free each dd

rough sample

Address ISPExec
'lminit dataid(ddb) ddname('ddn')'
'Edit dataid('ddb')'
'lmfree dataid('ddb')'
Address TSO,
  'Free f('ddn')'


On Fri, Jan 10, 2025 at 8:32 AM roscoe5
<056b62686b81-dmarc-requ...@listserv.ua.edu> wrote:
>
> I want to Edit a pair of files, from Prod and Test LPARs, both named 
> SYS1.TCPPARMS(PROFILE8), concurrently.
> I’m trying to make them as consistent as possible, with a lot of minor 
> changes to each.
> I have them both up in split screen (used their unique VOLSER) but I can only 
> have one or the other in Edit at a time, while the other is in View.
>
> Maybe there isn’t a way to do this, but if there is it would make things 
> easier.
>
> Thanks in advance!
>
> Sent from [Proton Mail](https://proton.me/mail/home) for iOS
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



--
Lionel B. Dyck <><
Website:https://github.com/lbdyck

"Worry more about your character than your reputation.  Character is
what you are, reputation merely what others think you are." - John
Wooden

--
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: ISPF Edit of same named files

[Lionel B Dyck]

I thought it would work but when I tried I get this:

 Ddname allocated to member of partitioned data set is not allowed.

guess my thought was a failure

On Fri, Jan 10, 2025 at 9:39 AM Schmitt, Michael
 wrote:
>
> How does this work? I'm thinking the OP's issue is that the SPFEDIT enqueue's 
> minor name is the library and member name, no volser. So even though they are 
> two different libraries, the enqueue blocks the 2nd edit.
>
> In my testing, you get the same SPFEDIT enqueue when use edit using a LMINIT 
> dataid. Which it would have to, because otherwise they're be a lot of PDS 
> corruption caused by simultaneous updates being allowed when one or more Edit 
> sessions are via a dialog.
>
>
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> Lionel B Dyck
> Sent: Friday, January 10, 2025 8:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: ISPF Edit of same named files
>
> use library services to do it
>
> 1. allocate each to a unique DD
> 2. use lminit on each dd
> 3. edit each using dataid
> 4. lmfree each when done
> 5. tso free each dd
>
> rough sample
>
> Address ISPExec
> 'lminit dataid(ddb) ddname('ddn')'
> 'Edit dataid('ddb')'
> 'lmfree dataid('ddb')'
> Address TSO,
>   'Free f('ddn')'
>
>
> On Fri, Jan 10, 2025 at 8:32 AM roscoe5
> <056b62686b81-dmarc-requ...@listserv.ua.edu> wrote:
> >
> > I want to Edit a pair of files, from Prod and Test LPARs, both named 
> > SYS1.TCPPARMS(PROFILE8), concurrently.
> > I’m trying to make them as consistent as possible, with a lot of minor 
> > changes to each.
> > I have them both up in split screen (used their unique VOLSER) but I can 
> > only have one or the other in Edit at a time, while the other is in View.
> >
> > Maybe there isn’t a way to do this, but if there is it would make things 
> > easier.
> >
> > Thanks in advance!
> >
> > Sent from [Proton Mail](https://proton.me/mail/home) for iOS
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>
>
> --
> Lionel B. Dyck <><
> Website:https://github.com/lbdyck
>
> "Worry more about your character than your reputation.  Character is
> what you are, reputation merely what others think you are." - John
> Wooden
>
> --
> 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



-- 
Lionel B. Dyck <><
Website:https://github.com/lbdyck

"Worry more about your character than your reputation.  Character is
what you are, reputation merely what others think you are." - John
Wooden

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

Re: Bye all

[Bfishing]

And while no longer active, this project from Marriott did show that Linux
on z running NodeJS with MongoDB could keep up with the speeds and feeds
required to replace TPF.
https://www.mongodb.com/blog/post/2019-mongodb-innovation-awards-winners

On Fri, Jan 10, 2025 at 1:40 AM Mike Schwab <
05962a42dc49-dmarc-requ...@listserv.ua.edu> wrote:

>
> https://planetmainframe.com/2023/06/sabre-is-getting-off-the-mainframe-one-way-or-another/
>
> On Thu, Jan 9, 2025 at 11:14 PM The North American Becker
> <0762a73125b7-dmarc-requ...@listserv.ua.edu> wrote:
> >
> > The mainframe is dead.
> >
> > --
> > 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
>


-- 

><º>`·.¸¸´¯`·.¸.·´¯`·...¸>(((º>
.·´¯`·.><º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><º>

<>< Go fishing ><>

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

Re: [EXTERNAL] ISPF Edit of same named files

[David Spiegel]

Hi Roscoe,
Edit one and View the other.

Regards,
David

On 2025-01-10 09:39, roscoe5 wrote:

Yep, that would work!
Simple solution, maybe more coffee, too.
I take it that what I was trying is indeed not allowed, and I wonder why not, 
but case closed.
Thanks!

Sent from [Proton Mail](https://proton.me/mail/home) for iOS

On Fri, Jan 10, 2025 at 9:35 AM, Pommier, Rex 
<[0737643a508d-dmarc-requ...@listserv.ua.edu](mailto:On Fri, Jan 10, 2025 at 9:35 
AM, Pommier, Rex < wrote:


Rename one of them temporarily?

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
roscoe5
Sent: Friday, January 10, 2025 8:32 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] ISPF Edit of same named files

I want to Edit a pair of files, from Prod and Test LPARs, both named 
SYS1.TCPPARMS(PROFILE8), concurrently.
I’m trying to make them as consistent as possible, with a lot of minor changes 
to each.
I have them both up in split screen (used their unique VOLSER) but I can only 
have one or the other in Edit at a time, while the other is in View.

Maybe there isn’t a way to do this, but if there is it would make things easier.

Thanks in advance!

Sent from [Proton 
Mail](https://urldefense.com/v3/__https://proton.me/mail/home__;!!KjMRP1Ixj6eLE0Fj!tLbv01a1C0WxpfHK6QmV8nvz-Z9JGIJiUY4fdGopMpWGtuWcn1s3jYdzTaa4g5uFWK1u3IAZkPPIDNBbBHfsNGYO5GOcQ8VSKV2x$
 ) for iOS

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


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

Re: ISPF Edit of same named files

[roscoe5]

Yep, call me lazy, but temporarily renaming a member was the best answer.

Sent from [Proton Mail](https://proton.me/mail/home) for iOS

On Fri, Jan 10, 2025 at 12:02 PM, Schmitt, Michael 
<[michael.schm...@dxc.com](mailto:On Fri, Jan 10, 2025 at 12:02 PM, Schmitt, 
Michael < wrote:

> Ah, a solution: write an Edit Interface (EDIF). Then your program is doing 
> the I/O, and ISPF Edit isn't doing the SPFEDIT enqueue.
>
> (but writing an Edit Interface is not easy!)
>
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> Lionel B Dyck
> Sent: Friday, January 10, 2025 9:44 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: ISPF Edit of same named files
>
> I thought it would work but when I tried I get this:
>
> Ddname allocated to member of partitioned data set is not allowed.
>
> guess my thought was a failure
>
> On Fri, Jan 10, 2025 at 9:39 AM Schmitt, Michael
>  wrote:
>>
>> How does this work? I'm thinking the OP's issue is that the SPFEDIT 
>> enqueue's minor name is the library and member name, no volser. So even 
>> though they are two different libraries, the enqueue blocks the 2nd edit.
>>
>> In my testing, you get the same SPFEDIT enqueue when use edit using a LMINIT 
>> dataid. Which it would have to, because otherwise they're be a lot of PDS 
>> corruption caused by simultaneous updates being allowed when one or more 
>> Edit sessions are via a dialog.
>>
>>
>> -Original Message-
>> From: IBM Mainframe Discussion List  On Behalf Of 
>> Lionel B Dyck
>> Sent: Friday, January 10, 2025 8:37 AM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: ISPF Edit of same named files
>>
>> use library services to do it
>>
>> 1. allocate each to a unique DD
>> 2. use lminit on each dd
>> 3. edit each using dataid
>> 4. lmfree each when done
>> 5. tso free each dd
>>
>> rough sample
>>
>> Address ISPExec
>> 'lminit dataid(ddb) ddname('ddn')'
>> 'Edit dataid('ddb')'
>> 'lmfree dataid('ddb')'
>> Address TSO,
>> 'Free f('ddn')'
>>
>>
>> On Fri, Jan 10, 2025 at 8:32 AM roscoe5
>> <056b62686b81-dmarc-requ...@listserv.ua.edu> wrote:
>> >
>> > I want to Edit a pair of files, from Prod and Test LPARs, both named 
>> > SYS1.TCPPARMS(PROFILE8), concurrently.
>> > I’m trying to make them as consistent as possible, with a lot of minor 
>> > changes to each.
>> > I have them both up in split screen (used their unique VOLSER) but I can 
>> > only have one or the other in Edit at a time, while the other is in View.
>> >
>> > Maybe there isn’t a way to do this, but if there is it would make things 
>> > easier.
>> >
>> > Thanks in advance!
>> >
>> > Sent from [Proton Mail](https://proton.me/mail/home) for iOS
>> >
>> > --
>> > For IBM-MAIN subscribe / signoff / archive access instructions,
>> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>
>>
>>
>> --
>> Lionel B. Dyck <><
>> Website:https://github.com/lbdyck
>>
>> "Worry more about your character than your reputation. Character is
>> what you are, reputation merely what others think you are." - John
>> Wooden
>>
>> --
>> 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
>
> --
> Lionel B. Dyck <><
> Website:https://github.com/lbdyck
>
> "Worry more about your character than your reputation. Character is
> what you are, reputation merely what others think you are." - John
> Wooden
>
> --
> 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

AutoIPL

[Steve Beaver]

How many of you have discovered the Auto IPL feature for zOS


Steve

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

Re: [EXTERNAL] ISPF Edit of same named files

[David Spiegel]

Hi Roscoe,
"... I’m a little surprised editing two unique files/members, coming 
from different VOLSERs, is a problem. ..."


Dataset ENQs do not include the VOLSER. That has been a problem since 
the beginning.
It also shows up when trying to RENAME/DELETE a Dataset (e,g, 
'SYS1,LINKLIB') which resides on a volume other than the one in actually 
in use.


A workaround for this is to:
RDEF FACILITY STGADMIN.DPDSRN.some.dataset UACC(NONE) OWNER(SYS1)
PE   STGADMIN.DPDSRN.* CL(FACILITY) ID(myuserid) AC(A)
SETR RACLIST(FACILITY) GENERIC(FACILITY) REF

where some.dataset is the DSN (up to 23 characters) to be RENAMED (or a 
mask for broader use)


Then, do a RENAME with VOLSER in ISPF Option 3.2

Regards,
David

On 2025-01-10 11:54, roscoe5 wrote:

Yes, David, that’s what I was doing. But going back and forth, getting out of 
Editing one so I could edit the other, was the (relatively minor) problem.
IF … if there had been an option to edit both at once, which renaming one/both 
supplies, that was what I was looking for.
I’m a little surprised editing two unique files/members, coming from different 
VOLSERs, is a problem.
But the main problem was my brain was not awake yet.
Thanks again, not just for today’s answer, but for all the help I see here 
daily.

Sent from [Proton Mail](https://proton.me/mail/home) for iOS

On Fri, Jan 10, 2025 at 10:28 AM, David Spiegel 
<[0468385049d1-dmarc-requ...@listserv.ua.edu](mailto:On Fri, Jan 10, 2025 at 10:28 
AM, David Spiegel < wrote:


Hi Roscoe,
Edit one and View the other.

Regards,
David

On 2025-01-10 09:39, roscoe5 wrote:

Yep, that would work!
Simple solution, maybe more coffee, too.
I take it that what I was trying is indeed not allowed, and I wonder why not, 
but case closed.
Thanks!

Sent from [Proton Mail](https://proton.me/mail/home) for iOS

On Fri, Jan 10, 2025 at 9:35 AM, Pommier, Rex 
<[0737643a508d-dmarc-requ...@listserv.ua.edu](mailto:On Fri, Jan 10, 2025 at 9:35 
AM, Pommier, Rex < wrote:


Rename one of them temporarily?

-Original Message-
From: IBM Mainframe Discussion List On Behalf Of 
roscoe5
Sent: Friday, January 10, 2025 8:32 AM
To:IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] ISPF Edit of same named files

I want to Edit a pair of files, from Prod and Test LPARs, both named 
SYS1.TCPPARMS(PROFILE8), concurrently.
I’m trying to make them as consistent as possible, with a lot of minor changes 
to each.
I have them both up in split screen (used their unique VOLSER) but I can only 
have one or the other in Edit at a time, while the other is in View.

Maybe there isn’t a way to do this, but if there is it would make things easier.

Thanks in advance!

Sent from [Proton 
Mail](https://urldefense.com/v3/__https://proton.me/mail/home__;!!KjMRP1Ixj6eLE0Fj!tLbv01a1C0WxpfHK6QmV8nvz-Z9JGIJiUY4fdGopMpWGtuWcn1s3jYdzTaa4g5uFWK1u3IAZkPPIDNBbBHfsNGYO5GOcQ8VSKV2x$
 ) for iOS

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

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

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

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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email tolists...@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: AutoIPL

[Ituriel do Neto]

Hello,

It is not new and I saw it working in a production environment, saving us a lot 
of time.
It is a nice feature.


Best Regards

Ituriel do Nascimento Neto
z/OS System Programmer






Em sexta-feira, 10 de janeiro de 2025 às 15:12:46 BRT, Steve Beaver 
<050e0c375a14-dmarc-requ...@listserv.ua.edu> escreveu: 





How many of you have discovered the Auto IPL feature for zOS


Steve

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

[Allan Staller]

Classification: Confidential

Discovered...Yes used (never)

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Steve Beaver
Sent: Friday, January 10, 2025 12:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AutoIPL

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

How many of you have discovered the Auto IPL feature for zOS


Steve

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

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.


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

Re: [EXTERNAL] ISPF Edit of same named files

[roscoe5]

Yes, David, that’s what I was doing. But going back and forth, getting out of 
Editing one so I could edit the other, was the (relatively minor) problem.
IF … if there had been an option to edit both at once, which renaming one/both 
supplies, that was what I was looking for.
I’m a little surprised editing two unique files/members, coming from different 
VOLSERs, is a problem.
But the main problem was my brain was not awake yet.
Thanks again, not just for today’s answer, but for all the help I see here 
daily.

Sent from [Proton Mail](https://proton.me/mail/home) for iOS

On Fri, Jan 10, 2025 at 10:28 AM, David Spiegel 
<[0468385049d1-dmarc-requ...@listserv.ua.edu](mailto:On Fri, Jan 10, 2025 
at 10:28 AM, David Spiegel < wrote:

> Hi Roscoe,
> Edit one and View the other.
>
> Regards,
> David
>
> On 2025-01-10 09:39, roscoe5 wrote:
>> Yep, that would work!
>> Simple solution, maybe more coffee, too.
>> I take it that what I was trying is indeed not allowed, and I wonder why 
>> not, but case closed.
>> Thanks!
>>
>> Sent from [Proton Mail](https://proton.me/mail/home) for iOS
>>
>> On Fri, Jan 10, 2025 at 9:35 AM, Pommier, Rex 
>> <[0737643a508d-dmarc-requ...@listserv.ua.edu](mailto:On Fri, Jan 10, 
>> 2025 at 9:35 AM, Pommier, Rex < wrote:
>>
>>> Rename one of them temporarily?
>>>
>>> -Original Message-
>>> From: IBM Mainframe Discussion List  On Behalf Of 
>>> roscoe5
>>> Sent: Friday, January 10, 2025 8:32 AM
>>> To: IBM-MAIN@LISTSERV.UA.EDU
>>> Subject: [EXTERNAL] ISPF Edit of same named files
>>>
>>> I want to Edit a pair of files, from Prod and Test LPARs, both named 
>>> SYS1.TCPPARMS(PROFILE8), concurrently.
>>> I’m trying to make them as consistent as possible, with a lot of minor 
>>> changes to each.
>>> I have them both up in split screen (used their unique VOLSER) but I can 
>>> only have one or the other in Edit at a time, while the other is in View.
>>>
>>> Maybe there isn’t a way to do this, but if there is it would make things 
>>> easier.
>>>
>>> Thanks in advance!
>>>
>>> Sent from [Proton 
>>> Mail](https://urldefense.com/v3/__https://proton.me/mail/home__;!!KjMRP1Ixj6eLE0Fj!tLbv01a1C0WxpfHK6QmV8nvz-Z9JGIJiUY4fdGopMpWGtuWcn1s3jYdzTaa4g5uFWK1u3IAZkPPIDNBbBHfsNGYO5GOcQ8VSKV2x$
>>>  ) for iOS
>>>
>>> --
>>> 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
>
> --
> 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: ISPF Edit of same named files

[Schmitt, Michael]

Ah, a solution: write an Edit Interface (EDIF). Then your program is doing the 
I/O, and ISPF Edit isn't doing the SPFEDIT enqueue.

(but writing an Edit Interface is not easy!)

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Lionel B Dyck
Sent: Friday, January 10, 2025 9:44 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ISPF Edit of same named files

I thought it would work but when I tried I get this:

 Ddname allocated to member of partitioned data set is not allowed.

guess my thought was a failure

On Fri, Jan 10, 2025 at 9:39 AM Schmitt, Michael
 wrote:
>
> How does this work? I'm thinking the OP's issue is that the SPFEDIT enqueue's 
> minor name is the library and member name, no volser. So even though they are 
> two different libraries, the enqueue blocks the 2nd edit.
>
> In my testing, you get the same SPFEDIT enqueue when use edit using a LMINIT 
> dataid. Which it would have to, because otherwise they're be a lot of PDS 
> corruption caused by simultaneous updates being allowed when one or more Edit 
> sessions are via a dialog.
>
>
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> Lionel B Dyck
> Sent: Friday, January 10, 2025 8:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: ISPF Edit of same named files
>
> use library services to do it
>
> 1. allocate each to a unique DD
> 2. use lminit on each dd
> 3. edit each using dataid
> 4. lmfree each when done
> 5. tso free each dd
>
> rough sample
>
> Address ISPExec
> 'lminit dataid(ddb) ddname('ddn')'
> 'Edit dataid('ddb')'
> 'lmfree dataid('ddb')'
> Address TSO,
>   'Free f('ddn')'
>
>
> On Fri, Jan 10, 2025 at 8:32 AM roscoe5
> <056b62686b81-dmarc-requ...@listserv.ua.edu> wrote:
> >
> > I want to Edit a pair of files, from Prod and Test LPARs, both named 
> > SYS1.TCPPARMS(PROFILE8), concurrently.
> > I’m trying to make them as consistent as possible, with a lot of minor 
> > changes to each.
> > I have them both up in split screen (used their unique VOLSER) but I can 
> > only have one or the other in Edit at a time, while the other is in View.
> >
> > Maybe there isn’t a way to do this, but if there is it would make things 
> > easier.
> >
> > Thanks in advance!
> >
> > Sent from [Proton Mail](https://proton.me/mail/home) for iOS
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>
>
> --
> Lionel B. Dyck <><
> Website:https://github.com/lbdyck
>
> "Worry more about your character than your reputation.  Character is
> what you are, reputation merely what others think you are." - John
> Wooden
>
> --
> 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



--
Lionel B. Dyck <><
Website:https://github.com/lbdyck

"Worry more about your character than your reputation.  Character is
what you are, reputation merely what others think you are." - John
Wooden

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

[Steve Beaver]

I have a friend that will not use AutoIPL for God , love , or money




This electronic mail (including any attachments) may contain information that 
is privileged, confidential, and/or otherwise protected from disclosure to 
anyone other than its intended recipient(s). Any dissemination or use of this 
electronic email or its contents (including any attachments) by persons other 
than the intended recipient(s) is strictly prohibited. If you have received 
this message in error, please notify us immediately by reply email so that we 
may correct our internal records. Please then delete the original message 
(including any attachments) in its entirety. Thank you


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Radoslaw Skorupka
Sent: Friday, January 10, 2025 1:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AutoIPL

W dniu 10.01.2025 o 19:12, Steve Beaver pisze:
> How many of you have discovered the Auto IPL feature for zOS

Me.
However it was looong time ago. 2016, or rather earlier.

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

Recovery question

[Joseph Reichman]

Hi 

I had been struggling with a estaex getting a return code of 8 until I
realized that ICANNT establish estaex in that environment

My question is if later after I establish the estatex recovery I  go so
supervisor state key zero will the recovery routine get control 


thanks  


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

Re: [EXTERNAL] Re: AutoIPL

[Wissink, Brad]

Know about it and used it.   prior employment we autoipl'd at 2:00 am on Sunday 
mornings once a month.

Brad Wissink| Sr. Systems Programmer
Sammons® Financial Group Member Companies
8300 Mills Civic Parkway, West Des Moines, Ia 50266
Phone 515-267-2735 | ext. 33735 | Cell: 515-231-1511 

bwiss...@sfgmembers.com  | www.SammonsFinancialGroup.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Steve Beaver
Sent: Friday, January 10, 2025 12:33 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: AutoIPL

I'm new to the USDOJ and my lead put in an IPL request for the sandbox - No big 
deal.

Well the operators got the system down and then auto magically the system 
Started coming up and I asked how??

In a no changes environment as that IPL was - it was quick - No HMC to 
manipulate 





-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Allan Staller
Sent: Friday, January 10, 2025 12:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AutoIPL

Classification: Confidential

Discovered...Yes used (never)

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Steve Beaver
Sent: Friday, January 10, 2025 12:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AutoIPL

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

How many of you have discovered the Auto IPL feature for zOS


Steve

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

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.


--
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: ISPF Edit of same named files

[Lionel B Dyck]

Here is a solution:

/* rexx */
'alloc f(jcl) ds(jcl.cntl) shr reuse'
address ispexec
'lminit dataid(jcl) ddname(jcl)'
'edit dataid('jcl') member($job)'
'edit dataid('jcl') member($jc)'
'lmfree dataid('jcl')'

Also if renaming is the approach why not just make a copy of the
member to edit and then copy it back.

On Fri, Jan 10, 2025 at 11:02 AM Schmitt, Michael
 wrote:
>
> Ah, a solution: write an Edit Interface (EDIF). Then your program is doing 
> the I/O, and ISPF Edit isn't doing the SPFEDIT enqueue.
>
> (but writing an Edit Interface is not easy!)
>
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> Lionel B Dyck
> Sent: Friday, January 10, 2025 9:44 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: ISPF Edit of same named files
>
> I thought it would work but when I tried I get this:
>
>  Ddname allocated to member of partitioned data set is not allowed.
>
> guess my thought was a failure
>
> On Fri, Jan 10, 2025 at 9:39 AM Schmitt, Michael
>  wrote:
> >
> > How does this work? I'm thinking the OP's issue is that the SPFEDIT 
> > enqueue's minor name is the library and member name, no volser. So even 
> > though they are two different libraries, the enqueue blocks the 2nd edit.
> >
> > In my testing, you get the same SPFEDIT enqueue when use edit using a 
> > LMINIT dataid. Which it would have to, because otherwise they're be a lot 
> > of PDS corruption caused by simultaneous updates being allowed when one or 
> > more Edit sessions are via a dialog.
> >
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List  On Behalf Of 
> > Lionel B Dyck
> > Sent: Friday, January 10, 2025 8:37 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: ISPF Edit of same named files
> >
> > use library services to do it
> >
> > 1. allocate each to a unique DD
> > 2. use lminit on each dd
> > 3. edit each using dataid
> > 4. lmfree each when done
> > 5. tso free each dd
> >
> > rough sample
> >
> > Address ISPExec
> > 'lminit dataid(ddb) ddname('ddn')'
> > 'Edit dataid('ddb')'
> > 'lmfree dataid('ddb')'
> > Address TSO,
> >   'Free f('ddn')'
> >
> >
> > On Fri, Jan 10, 2025 at 8:32 AM roscoe5
> > <056b62686b81-dmarc-requ...@listserv.ua.edu> wrote:
> > >
> > > I want to Edit a pair of files, from Prod and Test LPARs, both named 
> > > SYS1.TCPPARMS(PROFILE8), concurrently.
> > > I’m trying to make them as consistent as possible, with a lot of minor 
> > > changes to each.
> > > I have them both up in split screen (used their unique VOLSER) but I can 
> > > only have one or the other in Edit at a time, while the other is in View.
> > >
> > > Maybe there isn’t a way to do this, but if there is it would make things 
> > > easier.
> > >
> > > Thanks in advance!
> > >
> > > Sent from [Proton Mail](https://proton.me/mail/home) for iOS
> > >
> > > --
> > > For IBM-MAIN subscribe / signoff / archive access instructions,
> > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
> >
> >
> > --
> > Lionel B. Dyck <><
> > Website:https://github.com/lbdyck
> >
> > "Worry more about your character than your reputation.  Character is
> > what you are, reputation merely what others think you are." - John
> > Wooden
> >
> > --
> > 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
>
>
>
> --
> Lionel B. Dyck <><
> Website:https://github.com/lbdyck
>
> "Worry more about your character than your reputation.  Character is
> what you are, reputation merely what others think you are." - John
> Wooden
>
> --
> 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



-- 
Lionel B. Dyck <><
Website:https://github.com/lbdyck

"Worry more about your character than your reputation.  Character is
what you are, reputation merely what others think you are." - John
Wooden

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

What do I have to do to give myself permission to write into /etc ?

[Charles Mills]

I am more of a UNIX ignoramus than I should be. What do I have to do to give 
myself permission to write into /etc ?

Here is what /etc looks like:

Filename  Type Permission Audit  Ext  Fmat OwnerGroupLinks 
--- 
etc   Dir  rwxrwxr-x  fff---   OMVSKERN OMVSGRP  16

I can log on as IBMUSER and it accepts chmod u+rw /etc with no error but 
nothing changes.

What am I supposed to do? z/OS V3R1

Charles 

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

Re: AutoIPL

[Steve Beaver]

I'm new to the USDOJ and my lead put in an IPL request for the sandbox - No big 
deal.

Well the operators got the system down and then auto magically the system
Started coming up and I asked how??

In a no changes environment as that IPL was - it was quick - No HMC to 
manipulate 





-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Allan Staller
Sent: Friday, January 10, 2025 12:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AutoIPL

Classification: Confidential

Discovered...Yes used (never)

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Steve Beaver
Sent: Friday, January 10, 2025 12:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AutoIPL

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

How many of you have discovered the Auto IPL feature for zOS


Steve

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

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.


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

[David Purdy]

 The only problem with Autoipl is if an LPAR abends, it keeps on IPLing until 
operations or automated process notices
Happened once in five years
David
On Friday, January 10, 2025 at 01:33:15 PM EST, Steve Beaver 
<050e0c375a14-dmarc-requ...@listserv.ua.edu> wrote:  
 
 I'm new to the USDOJ and my lead put in an IPL request for the sandbox - No 
big deal.

Well the operators got the system down and then auto magically the system
Started coming up and I asked how??

In a no changes environment as that IPL was - it was quick - No HMC to 
manipulate 





-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Allan Staller
Sent: Friday, January 10, 2025 12:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AutoIPL

Classification: Confidential

Discovered...Yes used (never)

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Steve Beaver
Sent: Friday, January 10, 2025 12:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AutoIPL

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

How many of you have discovered the Auto IPL feature for zOS


Steve

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

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.


--
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: What do I have to do to give myself permission to write into /etc ?

[Charles Mills]

Solved it. Made myself a member of OMVSGRP.

Sorry for the disturbance to the force.

CM

On Fri, 10 Jan 2025 12:30:19 -0600, Charles Mills  wrote:

>I am more of a UNIX ignoramus than I should be. What do I have to do to give 
>myself permission to write into /etc ?
>
>Here is what /etc looks like:
>
>Filename  Type Permission Audit  Ext  Fmat OwnerGroupLinks 
>--- 
>etc   Dir  rwxrwxr-x  fff---   OMVSKERN OMVSGRP  16
>
>I can log on as IBMUSER and it accepts chmod u+rw /etc with no error but 
>nothing changes.
>
>What am I supposed to do? z/OS V3R1

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

Re: What do I have to do to give myself permission to write into /etc ?

[Shawn Prenevost]

"chmod 777 /etc" will add write to everyone

On Fri, Jan 10, 2025 at 12:30 PM Charles Mills  wrote:

> I am more of a UNIX ignoramus than I should be. What do I have to do to
> give myself permission to write into /etc ?
>
> Here is what /etc looks like:
>
> Filename  Type Permission Audit  Ext  Fmat OwnerGroupLinks
> ---
> etc   Dir  rwxrwxr-x  fff---   OMVSKERN OMVSGRP  16
>
> I can log on as IBMUSER and it accepts chmod u+rw /etc with no error but
> nothing changes.
>
> What am I supposed to do? z/OS V3R1
>
> Charles
>
> --
> 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: What do I have to do to give myself permission to write into /etc ?

[Michael Babcock]

What are the UIDs of OMVSKERN and IBMUSER?  If they are not the same and
IBMUSER’s UID is not 0, then IBMUSER will fall to either the group or
other. You can connect IBMUSER to OMVSGRP to get RW access to /etc.

If you are wanting YOUR ID to have RW access, connect yourself to OMVSGRP
(or chmod 777 but I wouldn’t recommend that).

On Fri, Jan 10, 2025 at 12:30 PM Charles Mills  wrote:

> I am more of a UNIX ignoramus than I should be. What do I have to do to
> give myself permission to write into /etc ?
>
> Here is what /etc looks like:
>
> Filename  Type Permission Audit  Ext  Fmat OwnerGroupLinks
> ---
> etc   Dir  rwxrwxr-x  fff---   OMVSKERN OMVSGRP  16
>
> I can log on as IBMUSER and it accepts chmod u+rw /etc with no error but
> nothing changes.
>
> What am I supposed to do? z/OS V3R1
>
> Charles
>
> --
> 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: What do I have to do to give myself permission to write into /etc ?

[Seymour J Metz]

Add OMVSGRP to your userid. Or su. 


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




From: IBM Mainframe Discussion List  on behalf of 
Charles Mills 
Sent: Friday, January 10, 2025 1:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: What do I have to do to give myself permission to write into /etc ?

External Message: Use Caution


I am more of a UNIX ignoramus than I should be. What do I have to do to give 
myself permission to write into /etc ?

Here is what /etc looks like:

Filename  Type Permission Audit  Ext  Fmat OwnerGroupLinks
---
etc   Dir  rwxrwxr-x  fff---   OMVSKERN OMVSGRP  16

I can log on as IBMUSER and it accepts chmod u+rw /etc with no error but 
nothing changes.

What am I supposed to do? z/OS V3R1

Charles

--
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: What do I have to do to give myself permission to write into /etc ?

[Radoslaw Skorupka]

W dniu 10.01.2025 o 19:30, Charles Mills pisze:

I am more of a UNIX ignoramus than I should be. What do I have to do to give 
myself permission to write into /etc ?

Here is what /etc looks like:

Filename  Type Permission Audit  Ext  Fmat OwnerGroupLinks
---
etc   Dir  rwxrwxr-x  fff---   OMVSKERN OMVSGRP  16

I can log on as IBMUSER and it accepts chmod u+rw /etc with no error but 
nothing changes.

What am I supposed to do? z/OS V3R1


The simplest way:
define CL(FACILITY) BPX.SUPERUSER profile and permit AUTH(READ) to your 
user.

Then you will be able to "su" command.
"su" means you want to be superuser vel batman vel superman vel Chuck 
Norris. You will be allowed to all possible filesystem actions despite 
of "rwx" settings.


However without the above a person with effective rwx (even less) is 
able to create file inside directory. Otherwise you should see ICH408I 
in the syslog. Did you observed any?
BTW: "write to /etc" mean write to a *directory* - it is not the same as 
write to file. w (write) to directory allows you to create or delete 
files inside. Even those files which you have no authority to even read. 
With different owner.


Advice: do not perform any test on /etc. Use some other directory 
instead. It can be /u/your_home/test_dir1



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

[Radoslaw Skorupka]

W dniu 10.01.2025 o 19:12, Steve Beaver pisze:

How many of you have discovered the Auto IPL feature for zOS


Me.
However it was looong time ago. 2016, or rather earlier.

--
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: [EXTERNAL] Re: AutoIPL

[Steve Beaver]

We have several other LPARs but currently I am only slightly familiar (3 weeks) 
with the SANDBOX LPAR

Thank you for your input  





-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Wissink, Brad
Sent: Friday, January 10, 2025 12:42 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: AutoIPL

Know about it and used it.   prior employment we autoipl'd at 2:00 am on Sunday 
mornings once a month.

Brad Wissink| Sr. Systems Programmer
Sammons® Financial Group Member Companies
8300 Mills Civic Parkway, West Des Moines, Ia 50266
Phone 515-267-2735 | ext. 33735 | Cell: 515-231-1511 

bwiss...@sfgmembers.com  | www.SammonsFinancialGroup.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Steve Beaver
Sent: Friday, January 10, 2025 12:33 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: AutoIPL

I'm new to the USDOJ and my lead put in an IPL request for the sandbox - No big 
deal.

Well the operators got the system down and then auto magically the system 
Started coming up and I asked how??

In a no changes environment as that IPL was - it was quick - No HMC to 
manipulate 





-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Allan Staller
Sent: Friday, January 10, 2025 12:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AutoIPL

Classification: Confidential

Discovered...Yes used (never)

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Steve Beaver
Sent: Friday, January 10, 2025 12:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AutoIPL

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

How many of you have discovered the Auto IPL feature for zOS


Steve

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

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.


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

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

Re: What do I have to do to give myself permission to write into /etc ?

[Paul Gilmartin]

On Fri, 10 Jan 2025 13:08:07 -0600, Shawn Prenevost wrote:

>"chmod 777 /etc" will add write to everyone
>
If that doesn't work, try RACF UACC=ALL.

-- 
gil

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

Re: ISREDIT CAPS ON OFF

[Bill Hitefield]

David,

Understood. I use REXX extensively for ISPF edit macros and such. I was 
agreeing that there were some "nice to have things" which clist did have. When 
I started, clist was the only way to go. Once we were introduced to REXX, I 
began converting clists to EXECs, and found WRITENR was a "clist only" entity. 
I agree with others in that the clist "PROC" could have been useful in REXX. I 
suspect most of us have written some sort of general-purpose parsing logic for 
use in REXX.

At this point, I have only a handful of clists which are still in use. Most are 
"1 time only" type things and are not worth converting.

Bill Hitefield
Dino-Software Corporation
800.480.DINO
www.dino-software.com

> -Original Message-
> From: IBM Mainframe Discussion List  On
> Behalf Of David Spiegel
> Sent: Thursday, January 9, 2025 7:26 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: ISREDIT CAPS ON OFF
> 
> Hi Bill,
> I also have an Exec which calls my Writenr clist.. My point was counter the
> idea that with Rexx, CLISTs are never necessary.
> 
> Regards,
> David
> 
> On 2025-01-09 19:18, Bill Hitefield wrote:
> > I wrote a dinky CLIST to issue WRITENR. I call it from REXX as needed.
> >
> > Bill Hitefield
> >
> >> -Original Message-
> >> From: IBM Mainframe Discussion List  On
> >> Behalf Of David Spiegel
> >> Sent: Thursday, January 9, 2025 5:42 PM
> >> To: IBM-MAIN@LISTSERV.UA.EDU
> >> Subject: Re: ISREDIT CAPS ON OFF
> >>
> >> Hi Tony,
> >> CLISTs also have the WRITENR statement, which Rexx lacks.
> >>
> >> Regards,.
> >> David
> >>
> >> On 2025-01-09 16:49, Tony Harminc wrote:
> >>> On Wed, 8 Jan 2025 at 19:51, Lennie Bradshaw
> >>> 
> >>> wrote:
> >>>
>  CLIST design is over 50 years old I think.
> 
> >>> CLISTs as we know them arrived with OS VS/2 Release 3, so the second
> >>> release of MVS around 1974 or so. Before that, on e.g MVT, SVS, and
> >>> the first MVS, CLISTs had no control flow statements - they were
> >>> just lists of commands with some substitution for arguments.
> >>>
> >>> At introduction, everyone was all excited at the shiny new CLISTs,
> >>> and I remember well wondering why there was no lower case support,
> >>> and if it could be easily fixed. Indeed it could, and I found and
> >>> happily zapped out the upcasing and tried a CLIST with some lower
> >>> case text in it. It blew up all over the place, and I discovered
> >>> that pretty much all byte values beyond the upper case letters,
> >>> numbers, and a few more (i.e. roughly the JCL character set at the
> >>> time) was being used as internal syntactic markers for various
> >>> aspects of the language. So much for
> >> that quick fix.
> >>> No, I don't remember the details, but I imagine much of today's
> >>> CLIST processor is unchanged from the 1970s version, and the source
> >>> code for that is available if anyone wants to research it further.
> >>>
> >>> But seriously, why does anyone use CLISTs today? There is to my
> >>> knowledge just one reason: there is tight integration with TSO
> >>> parsing and the CLIST header, whereas REXX requires that the command
> >>> be treated as a single string, and then parsed with the (unarguably
> >>> powerful)
> >> REXX parsing scheme.
> >>> But that doesn't allow for a syntax error to be discovered in the
> >>> REXX and the user prompted using TSO facilities; the REXX has to do
> >>> all the work itself.
> >>>
> >>> Tony H.
> >>>
> >>> 
> >>> -- 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
> 
> --
> 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