View previous topic :: View next topic
|
Author |
Message |
Willem Vermeer
New User
Joined: 31 Oct 2007 Posts: 38 Location: Amsterdam, the Netherlands
|
|
|
|
Greetings.
On some of our systems the following - very basic - ALLOCATE-command is failing now:
alloc da(test1) f(test1f) new space(1)
This command results in:
DATA SET Z537815.TEST1 NOT ALLOCATED+
IGD17051I ALLOCATION FAILED FOR DATA SET
Z537815.TEST1
, PRIMARY SPACE EXCEEDS 65535 TRKS
What does TSO/E take as the allocation-unit in this case and where does it get it from? We've checked ALLOCxx and IKJTSOxx and we cannot find it.
It's extra confusing, because we've never had it before. So something must have changed, but what?
Willem Vermeer
ING Bank
the Netherlands |
|
Back to top |
|
|
Escapa
Senior Member
Joined: 16 Feb 2007 Posts: 1399 Location: IL, USA
|
|
Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009 Posts: 1788 Location: Bloomington, IL
|
|
|
|
If I'm interpreting the fine manual correctly, the result of not specifying a SPACE unit on ALLOCATE is undefined, i.e., it may or may not work, and if it does work, that may change without notice or recourse.
If you have installed new versions of z/OS, MVS, or TSO, or PTFs to an or all of them, that's probably the cause. The solution, unfortunately, is either to back out the changes, or to correct the scripts with the failing ALLOCATEs. |
|
Back to top |
|
|
Willem Vermeer
New User
Joined: 31 Oct 2007 Posts: 38 Location: Amsterdam, the Netherlands
|
|
|
|
Sorry, but I've looked at the reference and it doesn't really help me. I know that I cannot allocate files with more than 64K tracks just like that.
My problem is, that I do not want to! This command allocates a 1 track file on other systems. So, why does it behave like this on this particular one? Why does it try to allocate a primary of that size and where does it get that number-of-tracks from?
I just say SPACE(1). Where does it get the SPACE-type from and why does it have such a large size? Which spacetype is it, anyway?
Willem Vermeer
ING Bank
the Netherlands |
|
Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009 Posts: 1788 Location: Bloomington, IL
|
|
|
|
I may have written unclearly; the undefined behavior is not that a data set with an allocation of 64K tracks cannot be created, but that the space type defaults to something that is less than 64K tracks. Again, I suggest that differences in system-level software between the systems where it succeeds and the system where it fails be looked at. |
|
Back to top |
|
|
nevilh
Active User
Joined: 01 Sep 2006 Posts: 262
|
|
|
|
Have you tried running the alloc with a non-sms managed dataset and seeing if that works. If this works the chances are someone has been playing with the ACS routine. |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
I usually use
It is all documented in the fine manuals |
|
Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006 Posts: 2547 Location: Silicon Valley
|
|
|
|
I agree that you need to specify the unit for the space value. Actually, I am surprised that you do not get some kind of 'required parameter missing' message. |
|
Back to top |
|
|
|