View previous topic :: View next topic
|
Author |
Message |
raghav08 Currently Banned New User
Joined: 03 Jun 2008 Posts: 94 Location: Bangalore
|
|
|
|
Hello,
I'm currently working in z/OS 01.10.00 environment, getting an error message - "UNIT FIELD SPECIFIES INCORRECT DEVICE NAME" for all jobs having
//xxx DUMMY UNIT=TAPE
UNIT=TAPE is working fine with remaining qualified datasets, but not with DUMMY statement.
//xxx DUMMY UNIT=DISK is working fine.
Please advice what's wrong with use of UNIT=TAPE for DUMMY.
Thanks
Raghav |
|
Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009 Posts: 2481 Location: Netherlands, Amstelveen
|
|
|
|
Is it me, or do i miss "DD" on the statement?
Something like :
//ddname DD DUMMY,other parameters |
|
Back to top |
|
|
raghav08 Currently Banned New User
Joined: 03 Jun 2008 Posts: 94 Location: Bangalore
|
|
|
|
Hello Peter,
"DD" exist in the JCL statement along with other parameters too, but i missed it in posting the query
Sorry...
Thanks,
Raghav |
|
Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009 Posts: 2481 Location: Netherlands, Amstelveen
|
|
|
|
So you still have a problem?
Why dont you show the jcl instead of giving some pieces (of crap). |
|
Back to top |
|
|
raghav08 Currently Banned New User
Joined: 03 Jun 2008 Posts: 94 Location: Bangalore
|
|
|
|
Yes still I have problem & sent a request to system support group.
Here is the piece of JCL...
//AMATAPE DD DUMMY,
// DISP=OLD,
// UNIT=TAPE,VOL=SER=,
// LABEL=(1,SL),
// DCB=(RECFM=U,BLKSIZE=1000)
I have tested same JCL by providing only parameter UNIT=TAPE (removed remaining all parameters), still not working.
But it's fine with UNIT=DISK |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
There is a link to manuals at the top of the page. Click it, find the JCL Language Reference manual, and you can read:
Quote: |
12.24 DUMMY Parameter
Parameter Type
Positional, optional
Purpose
Use the DUMMY parameter to specify that:
* No device or external storage space is to be allocated to the data set.
* No disposition processing is to be performed on the data set.
* For BSAM and QSAM, no input or output operations are to be performed on the data set. |
so DUMMY does not allow a device to be allocated to the DD name, yet when you say UNIT=TAPE you are requiring a device allocation. That is why the conflict and the message showing up. |
|
Back to top |
|
|
raghav08 Currently Banned New User
Joined: 03 Jun 2008 Posts: 94 Location: Bangalore
|
|
|
|
Robert,
But we are not getting any message with UNIT=DISK
(I hope that DISK too refers a device)
Please advice.
Thanks.. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Contact your site support group -- they can help. UNIT=DISK may or may not, depending upon your site, reference a device. |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
raghav08,
oh, you are so very clever...
i have noticed on newer z/OS with sms managed stuff (don't know if it has anything to do with it),
but my system gives me an error when I use DUMMY without a SPACE dcb parm.
UNIT=DISK will/can default automatically to a system defined device
where as
UNIT=TAPE can not default.
What I am trying to say
(and the storage guys will either beat me to death or allow my comment to go by with me unscathed)
is that DISK and TAPE although both are devices,
TAPE is not the same kind of device as DISK,
and defaults that allow for DISK to be considered as almost a comment,
do not allow for any reference to TAPE as a comment.
COMMENT ADDED:
Just noticed Robert's comment as I was posting this in the original form.
I explained it incorrectly,
but apparently had a feel for something that I did not understand. |
|
Back to top |
|
|
raghav08 Currently Banned New User
Joined: 03 Jun 2008 Posts: 94 Location: Bangalore
|
|
|
|
Hello All,
Now issue has been addressed by system support group.
//XXXX DD DUMMY,UNIT=TAPE is working fine.
Awaiting for resolution made by system support team.
Thanks |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Again, i'm late to the party. . .
Why is there a DD statement that specifies TAPE for a DUMMY dataset? |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
I must admit I'm baffled too, usually I just use
Code: |
//DDNAME DD DUMMY,RECFM=xx,LRECL=nnnn |
without any problems. |
|
Back to top |
|
|
Marso
REXX Moderator
Joined: 13 Mar 2006 Posts: 1353 Location: Israel
|
|
|
|
It reminds me of a joke:
A husband come home quite happy and says to his wife: today I missed the bus, I ran after it all the way back home, and I saved 4 dollars on the bus ticket.
To which the wife replies: you idiot, if you had run after a taxi you would have saved at least 20 dollars.
Using a dummy tape or a dummy disk, same difference as running after a bus or running after a taxi... |
|
Back to top |
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006 Posts: 1702 Location: Australia
|
|
|
|
Hi,
I don't ever remember overriding the UNIT parameter in a catalogue procedure regardless of the unit type when using DUMMY.
This was quite common the days when tape errors occurred (much more frequent than today) to rerun a job and only recreate the bad tape and dummying out other output files to save on tape drives.
Gerry |
|
Back to top |
|
|
Craq Giegerich
Senior Member
Joined: 19 May 2007 Posts: 1512 Location: Virginia, USA
|
|
|
|
It would be nice to know the message id! |
|
Back to top |
|
|
raghav08 Currently Banned New User
Joined: 03 Jun 2008 Posts: 94 Location: Bangalore
|
|
|
|
Hello.
We haven't changed JCL (nothing to do with application perspective), job went fine after system support team addressed the issue.
Solution : TAPE is in the active IODF now for all logical tapedrives
Thanks. |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
raghav08 wrote: |
Solution : TAPE is in the active IODF now for all logical tapedrives |
Now, this is something specific to your shop which Robert has already mentioned; your site-suport must have changed UNIT=TAPE not to reference a device now... |
|
Back to top |
|
|
|