In
![EMAIL PROTECTED],
on 12/08/2005
at 07:50 AM, Lizette Koehler [EMAIL PROTECTED] said:
If you just code a DD statement of
//DD1 DD DSN=datasetname
Then the default DISP is OLD,DELETE.
No. It's NEW,DELETE.
So if you are using
ALLOOCATE DSN(CENTER.UADS) DD(SYSUADS)
In [EMAIL PROTECTED],
on 12/08/2005
at 08:38 AM, Pommier, Rex R. [EMAIL PROTECTED] said:
I know the purists out there will jump on me for saying it is an
empty address
No, the purists will jump on you for presuming to speak for the
purists.
for saying it is an empty address space
No, that's
I'm with John here. Do code the DISP parameter. I especially recommend
this to newcomers.
The temporary work file cases you mention are surely candidates
for exception but aren't they often (mostly?) coded within
PROCs? And obsolete in many cases anyway.
What difference would it make if they
What difference would it make if they occur in a PROC? They are
hardly exceptions since they occur regularly (consider SMP/E and
utilities).
The thought was that PROCs are written and tested once but used
many times.
Why would you encourage newcomers to code a useless parameter under
those
Cross posted to IBM-MAIN and MVS-OE
FYI only.
Long time ago we discussed the expected versus the experienced
behaviour when doing an ls -l on a directory where you don't
have search permission.
Finally, IBM accepted an APAR for this problem:
OA01524: Z/OS UNIX V1.4 IS NOT CORRECTLY HANDLING
Hi:
In a recent post Johnny Luo wrote:
... However,when I execute the program via JCL without coding infile
DDNAME,it fails.
So I want to know the exact reason.My personal guess is that a job submitted
by JCL is not executed in
my TSO address space.Would someone be kind enough to give some
On 12/8/05, Terry Sambrooks [EMAIL PROTECTED] wrote:
If a batch job is submitted with PGM=IKJEFT10, IKJEFT1B or any of the
valid variations then whatever happens inside, be in REXX, Assembler, Cobol,
PLI, will run in a TSO environment, but not the same environment as that of
the submitter.
-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 08, 2005 2:19 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: 'ALLOCATE' a data set in my TSO/E session
I've dwell on some questions for days :
1,In TSO,I use 'listalc status' to find that SYS1.UADS has been
Johnny,
When allocating any dataset under TSO or BATCH I always ensure the DISP
parameter is properly set.
If you just code a DD statement of
//DD1 DD DSN=datasetname
Then the default DISP is OLD,DELETE. That means at job termination the data
set will be deleted. I will let
Lizette, the default DISP for existing datasets is OLD,KEEP, not OLD,DELETE.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 08, 2005 10:22 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: 'ALLOCATE' a data set in my TSO/E session
Johnny
AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: 'ALLOCATE' a data set in my TSO/E session
Lizette, the default DISP for existing datasets is OLD,KEEP, not
OLD,DELETE.
***
Bear Stearns is not responsible for any recommendation
: Thursday, December 08, 2005 10:22 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: 'ALLOCATE' a data set in my TSO/E session
Johnny,
When allocating any dataset under TSO or BATCH I always ensure the DISP
parameter is properly set.
If you just code a DD statement of
//DD1 DD DSN=datasetname
Peter,
Okay, I was remembering an incident where a Production IMS Reslib
disappeared because the application programmer coded (in the RESLIB
concatenation)
//DD DSN=reslib
And nothing else in the DD statement. When the IMS Control region came down
- it was deleted.
I think what I
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Lizette Koehler
Johnny,
When allocating any dataset under TSO or BATCH I always
ensure the DISP parameter is properly set.
If you just code a DD statement of
//DD1 DD DSN=datasetname
Then the
, 2005 10:32 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: 'ALLOCATE' a data set in my TSO/E session
Lizette, the default DISP for existing datasets is OLD,KEEP, not
OLD,DELETE.
_
This message and any attachments are intended only for the use of the addressee
and
may contain information
So, if you do not code a DISP on a DD statement then you will default
to NEW which creates an EXCL enq on the data set if it is in use by
another function. Once the function that allocated the file as default
NEW ends, it sets the DELETE bit
on the file. Then when all the other functions that
In [EMAIL PROTECTED], on
12/08/2005
at 03:14 PM, Luo Johnny [EMAIL PROTECTED] said:
1,In TSO,I use 'listalc status' to find that SYS1.UADS has been
allocated to DDNAME 'SYSUADS'. For a test, I issue
'allocate dsn(center.uads) dd(sysuads)' and get the meesage that
filename is in use. I
added to the EXEC statement for the VTAM
program, ISTINM01.
Chris Mason
- Original Message -
From: Gerhard Adam [EMAIL PROTECTED]
Newsgroups: bit.listserv.ibm-main
To: IBM-MAIN@BAMA.UA.EDU
Sent: Thursday, 08 December, 2005 11:47 PM
Subject: Re: 'ALLOCATE' a data set in my TSO/E session
So
I think what I should have said is the following:
If you do not code DISP you get the following conditions
DISP=(disp1,disp2,disp3)
If disp1 is not coded it will default to NEW
If disp2 is not coded it will default to DELETE for NEW or
KEEP for OLD
If disp3 is not coded it
As for never, ever, no way, should anybody never, ever not
use a DISP even if they want the default of NEW,DELETE, that
is also not realistic since it is done routinely when allocating
temporary work files like SORTWK and SYSUT1, etc. type files.
It clearly doesn't make sense to code a
I've dwell on some questions for days :
1,In TSO,I use 'listalc status' to find that SYS1.UADS has been allocated to
DDNAME 'SYSUADS'.
For a test, I issue 'allocate dsn(center.uads) dd(sysuads)' and get the
meesage that filename is
in use. I resort to manuals and know that to do this I
21 matches
Mail list logo
