In p06240805ce4d9305cf4f@[192.168.1.11], on 09/04/2013
at 09:55 PM, Robert A. Rosenberg hal9...@panix.com said:
Except for one MAJOR difference - PASS will leave the tape mounted
(although it might rewind it) while KEEP will unload the tape
Not if you specify RETAIN. Unfortunately, there's
In
caarmm9tsfrlc3zzj2fspy8kmu90crt8j714oxgvijlz7q4y...@mail.gmail.com,
on 09/03/2013
at 10:43 PM, Tony Harminc t...@harminc.net said:
But Dynalloc did not exist until MVS,
Not as a supported facility for user code, but it was there for use by
DAIR in TSO. As I recall, the interface was
On 4 September 2013 09:41, Shmuel Metz (Seymour J.)
shmuel+...@patriot.net wrote:
But Dynalloc did not exist until MVS,
Not as a supported facility for user code, but it was there for use by
DAIR in TSO. As I recall, the interface was different.
There was an SVC 99 in MVT, but it wasn't
At 09:41 -0400 on 09/04/2013, Shmuel Metz (Seymour J.) wrote about
Re: UNIT=SEP still alive (?):
True, but PASS is still intended for the situation where there is a
receiving DD in a subsequent step. Within the same step, KEEP and PASS
are equivalent.
Except for one MAJOR difference - PASS
At 23:57 -0500 on 09/03/2013, Ed Gould wrote about Re: UNIT=SEP still
alive (?):
On Sep 3, 2013, at 3:50 PM, Robert A. Rosenberg wrote:
MY memory from 20 years ago. NOT ALL Datasets are supported with SVC
99 (good indication is GDG but there are othrs).
If you say so. I see no reason why
W dniu 2013-09-02 19:54, Clark Morris pisze:
On 1 Sep 2013 07:03:23 -0700, in bit.listserv.ibm-main you wrote:
On 9/1/2013 6:47 AM, Tom Russell wrote:
In the case of multiple steps each allocating one file on the same
tape, and no AFF parameter used, there was (is?) a significant
difference
W dniu 2013-09-03 12:19, Paul Gilmartin pisze:
On 2013-09-03, at 00:05, R.S. wrote:
IMHO it's bad idea to use tapes for such operations. Tapes nowadays are for backups, dumps, ML2, etc. but not direct application use.
My €0.02
We are still committed to deliver some products (or at least
In 6708946340357622.wa.paulgboulderaim@listserv.ua.edu, on
09/02/2013
at 05:13 PM, Paul Gilmartin paulgboul...@aim.com said:
And what's the TU corresponding to PASS?
DALNDISP (0005) and DALCDISP (0006)with value X'02' is close. PASS is
intended for multi-step jobs, and TSO sessions are
On 3 September 2013 09:33, Shmuel Metz (Seymour J.)
shmuel+...@patriot.net wrote:
In 6708946340357622.wa.paulgboulderaim@listserv.ua.edu, on
09/02/2013
at 05:13 PM, Paul Gilmartin paulgboul...@aim.com said:
And what's the TU corresponding to PASS?
DALNDISP (0005) and DALCDISP
At 09:33 -0400 on 09/03/2013, Shmuel Metz (Seymour J.) wrote about
Re: UNIT=SEP still alive (?):
In 6708946340357622.wa.paulgboulderaim@listserv.ua.edu, on
09/02/2013
at 05:13 PM, Paul Gilmartin paulgboul...@aim.com said:
And what's the TU corresponding to PASS?
DALNDISP (0005
On Sep 3, 2013, at 3:50 PM, Robert A. Rosenberg wrote:
MY memory from 20 years ago. NOT ALL Datasets are supported with SVC
99 (good indication is GDG but there are othrs).
Ed
--
For IBM-MAIN subscribe / signoff / archive
On Sun, 1 Sep 2013 10:53:19 -0400, DanD wrote:
Device allocation for JES2 occurs at step initiation.
Each step would allocate a single device. If RETAIN was coded AVR would
recognize the mounted volume and reuse the same device for the next step.
Let's talk about DYNALLOC. AFAICT, DYNALLOC
On 1 Sep 2013 07:03:23 -0700, in bit.listserv.ibm-main you wrote:
On 9/1/2013 6:47 AM, Tom Russell wrote:
In the case of multiple steps each allocating one file on the same
tape, and no AFF parameter used, there was (is?) a significant
difference between JES2 and JES3.
For allocating tape
At 10:50 -0500 on 09/02/2013, Paul Gilmartin wrote about Re: UNIT=SEP
still alive (?):
Bruce Black once generously performed an experiment and concluded that
there's no way to DYNALLOC two or more data sets on the same volume
concurrently although JCL DD allocation has no problem
IIRC still need referback incrementing label as you go for multivolume files.
//DD1 LABEL=(1,SL)
//DD2 LABEL=(2,SL),VOL=REF=DD1
//DD3 LABEL=(3,SL),VOL=REF=DD2
In a message dated 09/02/13 15:31:09 Central Daylight Time, hal9...@panix.com
writes:
DISP=PASS handle this so the volume is not
On Mon, 2 Sep 2013 17:05:23 -0500, efinnell15 wrote:
IIRC still need referback incrementing label as you go for multivolume files.
//DD1 LABEL=(1,SL)
//DD2 LABEL=(2,SL),VOL=REF=DD1
//DD3 LABEL=(3,SL),VOL=REF=DD2
Yes, but I was trying to use DYNALLOC. POSITION is easy, but
what's the SVC 99 TU
In
CAE1XxDH4S9kUDN4T=psp43g0n_qpq7vkzo3syjct4z6qvkw...@mail.gmail.com,
on 08/30/2013
at 08:43 AM, John Gilmore jwgli...@gmail.com said:
SEP= dates back to the early days of OS/360, and it was then
unproblematic. Device addresses comprised of just three hexadecimal
digits were part numbers,
test this as I have no JES3 system.
Tom Russell
On 2013-09-01 12:00 AM, IBM-MAIN automatic digest system wrote:
Date:Sat, 31 Aug 2013 02:19:26 -0400
From:Gerhard Postpischilgerh...@valley.net
Subject: Re: UNIT=SEP still alive (?)
On 8/30/2013 9:22 PM, Robert A. Rosenberg wrote:
I know
On 9/1/2013 6:47 AM, Tom Russell wrote:
In the case of multiple steps each allocating one file on the same
tape, and no AFF parameter used, there was (is?) a significant
difference between JES2 and JES3.
JES2 would allocate as many tapes as there were steps, and rewind an
unload the volume
From: Tom Russell
...
JES2 would allocate as many tapes as there were steps, and rewind an
unload the volume after each step and issue a mount for the same volume
on the next tape drive.
...
Not quite Tom.
Device allocation for JES2 occurs at step initiation.
Each step would allocate a single
On 8/30/2013 9:22 PM, Robert A. Rosenberg wrote:
I know for multi-volume datasets UNIT=(TAPE,2) handled the mount of
volume3 while volume1 rewound and unloaded. I do not remember if you
could allocate 2 units and have concatenated input volumes alternate
between them. AVR might have helped since
redundant.
Ron
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of efinnell15
Sent: Friday, August 30, 2013 11:39 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] UNIT=SEP still alive (?)
We had one in early XA ESP where techy
W dniu 2013-08-29 23:09, Ted MacNEIL pisze:
I started as a JCL jockey in Prod Support, under MVS.
It was still supported, then (pre-XA).
-
Supported or just syntax-checked and ignored ?
--
Radoslaw Skorupka
Lodz, Poland
--
Treść tej wiadomości może zawierać informacje prawnie chronione
W dniu 2013-08-29 23:33, John Gilmore pisze:
The z/OS V1R9 MVS JCL Reference--The 12th edition of 2007 September
and the oldest one I have on my workstation--describes AFF, SEP,
SPLIT, and SUBALLOC as obsolete subparameters on page 5-18.
It's still there (at least at z/OS 1.13 level).
However
-To: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: UNIT=SEP still alive (?)
W dniu 2013-08-29 23:09, Ted MacNEIL pisze:
I started as a JCL jockey in Prod Support, under MVS.
It was still supported, then (pre-XA).
-
Supported or just syntax-checked and ignored
W dniu 2013-08-30 11:50, Ted MacNEIL pisze:
It seemed to work.
-
Tiny Harminc wrote:
I slightly more than vaguely remember it the same way. SEP=
disappeared (was ignored) with MVS, i.e. OS/VS2 2.0, because it
limited the then-new SRM's ability to swap a job in or out to control
the I/O
Tony Harminc wrote:
begin extract
And on that note, I even more vaguely remember that SEP= (in pre-MVS
OSs) was done at the channel level rather then the device, but that's
so vague as to be unreliable.
/end extract
and, unlike many such, this particular vague memory is veridical.
SEP= dates
On 29 Aug 2013 20:39:00 -0700, in bit.listserv.ibm-main you wrote:
On Thu, Aug 29, 2013 at 6:25 PM, Clark Morris cfmpub...@ns.sympatico.ca
wrote:
On 29 Aug 2013 14:33:21 -0700, in bit.listserv.ibm-main you wrote:
The z/OS V1R9 MVS JCL Reference--The 12th edition of 2007 September
and the
We had one in early XA ESP where techy changed a few jobs and had UNIT=3800 for
SORTWKs and it tried to honor it. Can you say wreck?
In a message dated 08/30/13 13:23:33 Central Daylight Time, gerh...@valley.net
writes:
He reported that a CoBOL programmer submitted a sort job with
all sort
On 08/30/2013 08:44 AM, Clark Morris wrote:
On 29 Aug 2013 20:39:00 -0700, in bit.listserv.ibm-main you wrote:
On Thu, Aug 29, 2013 at 6:25 PM, Clark Morris cfmpub...@ns.sympatico.ca
wrote:
On 29 Aug 2013 14:33:21 -0700, in bit.listserv.ibm-main you wrote:
The z/OS V1R9 MVS JCL
At 14:23 -0400 on 08/30/2013, Gerhard Postpischil wrote about Re:
UNIT=SEP still alive (?):
This appears to be a no-win situation for IBM. Our systems used AVR, and
had enough drives, so that for us it was more important to reduce tape
mount delays (while the job sat occupying limited storage
I just found the following in some IBM same JCL (job, actually):
//SYSUT1 DD UNIT=(SYSDA,SEP=(SORTLIB,SYSLMOD,SYSLIN)),
// SPACE=(1000,(60,20))
Last change date is half of the 2013 (creation date is probably 2005 or so).
As far as I know SEP is syntax checked and ignored for many moons, at
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: UNIT=SEP still alive (?)
I just found the following in some IBM same JCL (job, actually):
//SYSUT1 DD UNIT=(SYSDA,SEP=(SORTLIB,SYSLMOD,SYSLIN)),
// SPACE=(1000,(60,20))
Last change date is half of the 2013 (creation date is probably 2005 or so).
As far as I know
W dniu 2013-08-29 22:48, Pommier, Rex R. pisze:
OK, what does (did) SEP= do? The only thing the JCL reference says is that you
can't use it as a JCL symbol in certain types of jobs.
See ancient (really old!) version of JCL manual. I don't have any here,
but my failing memory says it was used
use it as a JCL symbol in certain types of jobs.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of R.S.
Sent: Thursday, August 29, 2013 3:18 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: UNIT=SEP still alive (?)
I just found
On 2013-08-29 14:56, John McKown wrote:
SEP= was supposed to guarantee that the data sets were placed on SEParate
volumes. Likely to enhance concurrent I/O overlap.
This was probably most effective if yours was the only job
running in the system at that instant.
On Thu, Aug 29, 2013 at 3:48
Date: Thu, 29 Aug 2013 15:56:49
To: IBM-MAIN@LISTSERV.UA.EDU
Reply-To: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: UNIT=SEP still alive (?)
SEP= was supposed to guarantee that the data sets were placed on SEParate
volumes. Likely to enhance concurrent I/O
it as a JCL symbol in certain types of jobs.
:
:-Original Message-
:From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of R.S.
:Sent: Thursday, August 29, 2013 3:18 PM
:To: IBM-MAIN@LISTSERV.UA.EDU
:Subject: UNIT=SEP still alive (?)
:
:I just found the following
It was also useful when creating a backup so that the backup was not on the
same device as the original.
I noticed this...
JCL example
z/OS V1R12.0 Metal C Programming Guide and Reference
SA23-2225-03
...
//SYSUT1 DD UNIT=(SYSDA,SEP=SYSLIB),SPACE=(CYL,(10,5)),DSN=SYSUT1
Dan
-Original
The z/OS V1R9 MVS JCL Reference--The 12th edition of 2007 September
and the oldest one I have on my workstation--describes AFF, SEP,
SPLIT, and SUBALLOC as obsolete subparameters on page 5-18.
John Gilmore, Ashland, MA 01721 - USA
On 29 Aug 2013 14:33:21 -0700, in bit.listserv.ibm-main you wrote:
The z/OS V1R9 MVS JCL Reference--The 12th edition of 2007 September
and the oldest one I have on my workstation--describes AFF, SEP,
SPLIT, and SUBALLOC as obsolete subparameters on page 5-18.
I can see SEP, SPLIT and SUBALLOC
In
3ebf9c9d119fd847b3a096c515a018f6949e4...@surfsdvmp35.cnasurety.net,
on 08/29/2013
at 08:48 PM, Pommier, Rex R. rex.pomm...@cnasurety.com said:
OK, what does (did) SEP= do?
Separated allocations on different devices; think of it as the
opposite of AFF.
--
Shmuel (Seymour J.) Metz,
At 20:48 + on 08/29/2013, Pommier, Rex R. wrote about Re:
UNIT=SEP still alive (?):
OK, what does (did) SEP= do? The only thing the JCL reference says
is that you can't use it as a JCL symbol in certain types of jobs.
Others have also answered. To expand on what they said, UNIT=SYSDA
On 29 August 2013 16:18, R.S. r.skoru...@bremultibank.com.pl wrote:
I just found the following in some IBM same JCL (job, actually):
//SYSUT1 DD UNIT=(SYSDA,SEP=(SORTLIB,SYSLMOD,SYSLIN)),
// SPACE=(1000,(60,20))
Last change date is half of the 2013 (creation date is probably 2005 or so).
As
44 matches
Mail list logo
