Sorry, Frank, I tested this before posting, but unfortunately
as it seems, I was somehow fooled, i.e. I did not test precise
enough.
I stand corrected. It does not work the way I was telling here.
I overlooked that simple message in then JESYSMSG file:
IEF694I DDNAME REFERENCE TO DD
On Tue, 18 Nov 2008 10:03:07 +0100, Hunkeler Peter (KIUK 3)
[EMAIL PROTECTED] wrote:
Sorry, Frank, I tested this before posting, but unfortunately
as it seems, I was somehow fooled, i.e. I did not test precise
enough.
I stand corrected. It does not work the way I was telling here.
I overlooked
On Mon, 17 Nov 2008 08:47:06 +0100, Hunkeler Peter (KIUK 3)
[EMAIL PROTECTED] wrote:
I had an example in my post where 3 libraries where defined
through one //OWNSYSLB DD. Isn't this what you're talking about?
You can concatenate many PDSs, PDSEs and even UNIX directories
with a single DD (The
On Sat, 15 Nov 2008 08:25:18 -, Terry Sambrooks
[EMAIL PROTECTED] wrote:
Hi Frank,
In answer to your query about the default UNIT and SPACE in the following:
[deleted]
If the output listing is checked it might help explain what has happened.
The SYSUT1 override should appear ahead of its
As for the OWNSYSLB statement, the problem with that is it does
not work to add more than a single library.
I had an example in my post where 3 libraries where defined
through one //OWNSYSLB DD. Isn't this what you're talking about?
You can concatenate many PDSs, PDSEs and even UNIX directories
Hi Frank,
In answer to your query about the default UNIT and SPACE in the following:
Here's a sort of unrelated question that it brings to mind. I notice in
the IBM
supplied Cobol compile procs they specify work files like this:
//SYSUT1 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
I just made my
Now how is *this* one for interesting:
You specifically were looking for a solution where you
did not have to estimate the muximum number of libraries
to concatenate ahead of the given library. This is why
I came up with the DDNAME=OWNSYSLB propsal. Additional
advantage: Your users do not need
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Frank Swarbrick
Now how is *this* one for interesting:
//COBOL PROC COBOPT=
//COB EXEC PGM=IGYCRCTL,REGION=4096K,PARM='COBOPT'
//SYSIN DD DISP=SHR,DSN=FJS.PDSE.COBOL(MEMBER)
//SYSPRINT DD SYSOUT=*
On Fri, 14 Nov 2008 09:33:23 +0100, Hunkeler Peter (KIUK 3)
[EMAIL PROTECTED] wrote:
Now how is *this* one for interesting:
You specifically were looking for a solution where you
did not have to estimate the muximum number of libraries
to concatenate ahead of the given library. This is why
I
On Fri, 14 Nov 2008 09:05:52 -0600, Chase, John [EMAIL PROTECTED]
wrote:
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Frank Swarbrick
Now how is *this* one for interesting:
//COBOL PROC COBOPT=
//COB EXEC PGM=IGYCRCTL,REGION=4096K,PARM='COBOPT'
On Fri, 14 Nov 2008 12:59:13 -0600, Frank Swarbrick wrote:
Here's a sort of unrelated question that it brings to mind. I notice in
the IBM
supplied Cobol compile procs they specify work files like this:
//SYSUT1 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
I just made my own version and changed these
On Fri, 14 Nov 2008 14:16:33 -0600, Tom Marchant m42tom-
[EMAIL PROTECTED] wrote:
The UNIT is not necessary for SMS-managed DASD data sets.
The space was probably provided by the DATACLAS that was
assigned to your data set. See your Systems Programmer.
Will do. Thanks again!
Frank
Now how is *this* one for interesting:
//COBOL PROC COBOPT=
//COB EXEC PGM=IGYCRCTL,REGION=4096K,PARM='COBOPT'
//SYSIN DD DISP=SHR,DSN=FJS.PDSE.COBOL(MEMBER)
//SYSPRINT DD SYSOUT=*
// INCLUDE
=FJS.PDSE.COBOL
// DD
// DD DISP=SHR,DSN=FJS.TEST.COBOL
Date: Thu, 13 Nov 2008 11:52:06 -0600
From: [EMAIL PROTECTED]
Subject: concatenations, again
To: IBM-MAIN@BAMA.UA.EDU
Now how is *this* one for interesting:
//COBOL PROC COBOPT=
//COB EXEC PGM=IGYCRCTL,REGION=4096K,PARM='COBOPT
14 matches
Mail list logo
