Re: Data space dump with SDUMPX

2024-02-01 Thread Binyamin Dissen
This seems to suggest that the dataspace name does not exist under this memory. Try specifying your jobname and "*" for the dataspace name. See what comes out. On Wed, 31 Jan 2024 13:23:33 +0100 Schühle, Simon wrote: :>Ok, LDMP is what I used until now to check the dump contents. So that's

Re: Connect:Direct question

2024-02-01 Thread Rasmussen, A. (Andre)
Hi Gadi Those aren't SYSOPTS options. You need to code it something like this. CPYSEQ PROCESS- SNODE=RTST COPY1 COPY- FROM (DSN=G120NTN.KVTNKSP.UNLOAD- DISP=SHR

Re: Data space dump with SDUMPX

2024-02-01 Thread Peter Relson
The DSPLIST indicated * One entry (based on the length) * Jobname of "*" * Dataspace name of 1EDB The SDUMP requested only the current ASID. I'd guess that the system will only try to dump data spaces owned by ASID's that are being dumped (or a data space that is SCOPE=COMMON,

Re: Generating output in SORT with a time value

2024-02-01 Thread Massimo Biancucci
Billy, as Sri said there's no way to ask SORT tools to put a different TS on every record. Hereby a "try" to start with an arbitrary TS (in TOD format to generate as you like) and then generate a number of consecutive TS part (HHMMSSuu) with a distance of 1 us. It's a two steps and probably

Re: Data space dump with SDUMPX

2024-02-01 Thread Jim Mulder
What is displayed by this IPCS command for your dump? CBF RTCT Jim Mulder -Original Message- From: IBM Mainframe Discussion List On Behalf Of Schühle, Simon Sent: Thursday, February 1, 2024 8:17 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Data space dump with SDUMPX So, just some

Re: Data space dump with SDUMPX

2024-02-01 Thread Schühle , Simon
Well, this does result in none of the data spaces I am looking for showing up in the dump. Many others show up, so I suspect that the limit for the amount of dumped data spaces was reached before. But also, when using the DUMP command, the correct data space is included in the dump. Wouldn't

Re: Replacement for LMAC program in ISPF 3.1

2024-02-01 Thread Lionel B. Dyck
This would work great if IBM hadn't also changed some control block offsets ☹ Lionel B. Dyck <>< Github: https://github.com/lbdyck System Z Enthusiasts Discord: https://discord.gg/system-z-enthusiasts-880322471608344597 “Worry more about your character than your reputation. Character is what

Re: ISPF Line Command Table (was LMAC)

2024-02-01 Thread Lionel B. Dyck
Hank - great point. This is great but the LMAC tool was dynamic and didn't require exiting Edit/View to return to pick up the new table. Cheers Lionel B. Dyck <>< Github: https://github.com/lbdyck System Z Enthusiasts Discord: https://discord.gg/system-z-enthusiasts-880322471608344597 “Worry

Re: Data space dump with SDUMPX

2024-02-01 Thread Schühle , Simon
So, just some additional details. My DUMP Command would look like this: DUMP COMM=(DSPTST),DSPNAME=('*'.1EDB),SDATA=(SUM,CSA,RGN),END Compared to the SDUMPX code I posted earlier, it's basically the same. But with DUMP I get the following result in the dump: ASID(X'0092') DSPNAME(1EDB)

Re: Connect:Direct question

2024-02-01 Thread Gadi Ben-Avi
Hi, I tried that but it didn't work. The manual says that the SMS parameters must be specified in the SYSOPTS. Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Rasmussen, A. (Andre) Sent: יום ה 01 פברואר 2024 11:34 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re:

Re: Connect:Direct question

2024-02-01 Thread Rasmussen, A. (Andre)
Hi It works on my end. The only difference is I have a generic process and then I pass the parameters to via my DMBATCH step in the JCL. I don't have a DATACLAS specified but as you can see the parameters are specified directly in the TO statement. DMBATCH JCL: //ST01#01 EXEC PGM=DMBATCH

Re: Antiquarian Curiosity: Pre-MVS/XA Mount Command for DASD Volumes

2024-02-01 Thread Michael Watkins
Wow! I did not realize that this was still part of the system console command documentation. Thanks! Thanks to all that replied. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jim Mulder Sent: Thursday, February 1, 2024 11:25 AM To: IBM-MAIN@LISTSERV.UA.EDU

Re: Connect:Direct question

2024-02-01 Thread Michael Oujesky
Food for thought. You might investigate using the ADRDSSU exit available to C:D. Not only does it allow specifying target dataset(s) SMS classes, it even allows copying whole volumes or dsname-masked groups of files between z/OS systems. Michael At 07:50 AM 1/31/2024, Gadi Ben-Avi wrote:

Difference between STSI instruction and SYSEVENT QVS?

2024-02-01 Thread Joe Monk
What (if any) is the difference between the STSI instruction and the SYSEVENT QVS service, other than maybe the C interface? Thanks, Joe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: JES2 JOBDEF DUPL_JOB=NODELAY - Any gotchas?

2024-02-01 Thread Robert Prins
Doing this regularly, my biggest problem is that a set of jobs running ISPF in batch, all with //ISPPROF set to a temporary dataset fall over, because it's in use. Adding a second or so delay between submitting them solves the issue, most of the time. On Thu, 1 Feb 2024, 19:15 Charles Mills,

Re: Antiquarian Curiosity: Pre-MVS/XA Mount Command for DASD Volumes

2024-02-01 Thread David Spiegel
Hi Michael, M cuu,VOL=(SL,volser),USE=STORAGE (or PUBLIC, PRIVATE) Regards, David On 2024-02-01 11:42, Michael Watkins wrote: Before MVS/XA and RAID DASD, offline DASD volumes (e.g. 3330, 3350 & 3380 units) had to be mounted instead of simply being varied online. The mount command used the

JES2 JOBDEF DUPL_JOB=NODELAY - Any gotchas?

2024-02-01 Thread Charles Mills
I am not a sysprog but I occasionally play one in my spare time. I am thinking of changing a system that I control to DUPL_JOB=NODELAY. Any gotchas? Anything I need to consider before I do this? Do most/many of you run with NO_DELAY? I am trying to solve a problem where I have jobs delayed

Antiquarian Curiosity: Pre-MVS/XA Mount Command for DASD Volumes

2024-02-01 Thread Michael Watkins
Before MVS/XA and RAID DASD, offline DASD volumes (e.g. 3330, 3350 & 3380 units) had to be mounted instead of simply being varied online. The mount command used the volser of the offline DASD volume as a parameter. Does anyone remember the format of the mount command? Does anyone have the

Re: Antiquarian Curiosity: Pre-MVS/XA Mount Command for DASD Volumes

2024-02-01 Thread Jay Maynard
M addr,VOL=(SL,volser),USE={PUBLIC|PRIVATE|STORAGE} There are those of us who use that command frequently when building not-current versions of MVS... On Thu, Feb 1, 2024 at 10:44 AM Michael Watkins < 032966e74d0f-dmarc-requ...@listserv.ua.edu> wrote: > Before MVS/XA and RAID DASD, offline

Ent. COBOL User-defined function question

2024-02-01 Thread Peter Farley
Using the listserv web interface for the first time, so I hope this goes through OK. In testing the new V6.4 user-defined functions capability I have found that it seems you cannot have a separately-compiled-and-linked user-defined function. If you separately compile and link the function for

Re: Antiquarian Curiosity: Pre-MVS/XA Mount Command for DASD Volumes

2024-02-01 Thread Michael Watkins
Thanks! Sorry if you took umbrage at 'antiquarian'; no offense intended. Question: Was 'PRIVATE' the default value for the USE parameter? -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jay Maynard Sent: Thursday, February 1, 2024 10:48 AM To:

Re: Antiquarian Curiosity: Pre-MVS/XA Mount Command for DASD Volumes

2024-02-01 Thread Jim Mulder
https://www.ibm.com/docs/en/zos/3.1.0?topic=reference-mount-command Jim Mulder -Original Message- From: IBM Mainframe Discussion List On Behalf Of Michael Watkins Sent: Thursday, February 1, 2024 11:43 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Antiquarian Curiosity: Pre-MVS/XA Mount

Re: EXTERNAL EMAIL: JES2 JOBDEF DUPL_JOB=NODELAY - Any gotchas?

2024-02-01 Thread Jerry Whitteridge
Biggest issue from my perspective is if all these jobs are on Initiators (rather than delayed in the input queue) how much are they count to block each other with dataset contention etc. Theres a possibility for some to even get into deadly embraces where 2 jobs lock each other out and can

Re: EXTERNAL EMAIL: JES2 JOBDEF DUPL_JOB=NODELAY - Any gotchas?

2024-02-01 Thread Seymour J Metz
You only get that deadly embrace with dynamic allocation. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר From: IBM Mainframe Discussion List on behalf of Jerry Whitteridge Sent: Thursday,

Re: Antiquarian Curiosity: Pre-MVS/XA Mount Command for DASD Volumes

2024-02-01 Thread Seymour J Metz
Not quite. You could use a unit after the vary, but you needed the MOUNT command to assign volume attributes. SMS largely made that irrelevant. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר

Re: Antiquarian Curiosity: Pre-MVS/XA Mount Command for DASD Volumes

2024-02-01 Thread Lennie Dymoke-Bradshaw
I still use MOUNT commands on my zPDT z/OS 3.1 system to bring new volumes online, in flight. It would be similarly used, I think, if new DASD was made available on any system. Lennie Dymoke-Bradshaw -Original Message- From: IBM Mainframe Discussion List On Behalf Of Michael Watkins

Re: EXTERNAL EMAIL: JES2 JOBDEF DUPL_JOB=NODELAY - Any gotchas?

2024-02-01 Thread Michael Oujesky
And poorly designed applications that dynamically request the same resources exclusively, but in a different order in various separate instances. Michael At 01:46 PM 2/1/2024, Seymour J Metz wrote: Content-Transfer-Encoding: base64You only get that deadly embrace with dynamic allocation.

Re: Antiquarian Curiosity: Pre-MVS/XA Mount Command for DASD Volumes

2024-02-01 Thread Seymour J Metz
It's still relevant if you're not using SMS. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר From: IBM Mainframe Discussion List on behalf of Willy Jensen Sent: Thursday, February 1, 2024

Re: Antiquarian Curiosity: Pre-MVS/XA Mount Command for DASD Volumes

2024-02-01 Thread Mike Schwab
Still relevant for all non-SMS volumes. On Thu, Feb 1, 2024 at 4:42 PM Seymour J Metz wrote: > It's still relevant if you're not using SMS. > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > עַם יִשְׂרָאֵל חַי > נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר > >

Re: Antiquarian Curiosity: Pre-MVS/XA Mount Command for DASD Volumes

2024-02-01 Thread Willy Jensen
Seems that the VATLSTxx parmlib member is still relevant. From the z/OS 2.5 MVS Initialization and Tuning Reference: The VATLSTxx member contains an optional VATDEF statement followed by entries that define the mount and use attributes of DASD volumes. Use the VATDEF statement in VATLSTxx to