|
View previous topic :: View next topic
|
| Author |
Message |
chetanambi
New User
Joined: 21 Jan 2012
Posts: 58
Location: India
|
|
|
|
Hello there,
I am trying to transmit an ESDS file thru NDM and getting below error message "SMS DYNAMIC ALLOCATION error" . I googled for the answers but didn't get answer. I do have access to create file in receiving node. NDM process is working fine for flat files and KSDS file but not working for this ESDS file.
Can someone please give me pointers to analyse further. |
|
| Back to top |
|
 |
mistah kurtz
Active User
Joined: 28 Jan 2012
Posts: 316
Location: Room: TREE(3). Hilbert's Hotel
|
|
|
|
| Did you search with the error code that you are getting, something similar to SDEXXXI. |
|
| Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007
Posts: 2454
Location: Hampshire, UK
|
|
|
|
| Not really - you have presented 4 words out of all your messages - no message ID no other possible helpful messages. What did your storage people say? |
|
| Back to top |
|
|
chetanambi
New User
Joined: 21 Jan 2012
Posts: 58
Location: India
|
|
|
|
This the detail from NDM tool.
| Code: |
CMD ==>
SMS DYNAMIC ALLOCATION error.
Process Name : COPYTDF Submtr: xxxxxxxx.xxxx DBCS:
Userid : YYYYY
Other Addr: xxxxx;xx.xx.xx.xx
Process Number : 43,222 Other Node: xxxx.xxxxx.xxx P|Snode : PNODE
Starting Time : 01:04:55 Date : 05/03/2017 Sending Node : PNODE
Ending Time : 01:04:55 Date : 05/03/2017 RC : 00000008
Step Name : STEP01 Rusize : 8,192 MSGID : SDE970CI
Server : PLEXCLASS : ( )
Secure Plus : NOT USED
*OTHER_NODE* * COMP-EXT *
SENDING DSN : Pxxx.xXX.xxx.xxx.xxxFILEA
Block count : 0 Records : 0 RUs : 0
I/O Bytes: 0 VTAM bytes: 0
Members : 0 Aliases : 0 Comp% 0.0%
Members ¬Sent : 0 Aliases ¬Sent : 0
RECEIVE DSN : TTO2.xXX.xxx.xxx.xxxFILEA
Block count : 0 Records : 0 RUs : 0
I/O Bytes: 0 VTAM bytes: 0
Members : 0 Aliases : 0 Comp% 0.0%
1st 8 volumes :
|
|
|
| Back to top |
|
|
chetanambi
New User
Joined: 21 Jan 2012
Posts: 58
Location: India
|
|
|
|
I just noticed MSGID SDE970CI from my above message.
SDE970CI
MODULE =DMGDYNAL
SMS DYNAMIC ALLOCATION error.
An error was detected while trying to dynamically allocate
a file. The error code returned from SMS (Systems
Managed Storage) was 970C.
Some causes are: dataset allocated with NEW already exists;
Insufficient access authority (security); Out of space or
out of extents on the volume; Invalid high level index.
RESPONSE: Do a Select Statistics on the process that failed.
Include WTOs in the selection criteria. Look for WTOs
prefixed with SDAASMSI for further details. Also, look at the
system log for related SMS or security messages. |
|
| Back to top |
|
|
chetanambi
New User
Joined: 21 Jan 2012
Posts: 58
Location: India
|
|
|
|
In response to possible causes as per the MSGID SDE970CI
1. Verified that dataset does not exist in receiving node
2. I am able to NDM flat file and KSDS files so I think I have sufficient authority for this file as well.
3. I tried by increasing the space from UI but still getting same error.
4. Invalid high level index- not sure how to check this. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8700
Location: Dubuque, Iowa, USA
|
|
|
|
| Quote: |
| 4. Invalid high level index- not sure how to check this |
On the receiving system, go to ISPF 3.4 and put in the high level index (the first part of the data set name up to the and not including the period), then hit enter. If ANYTHING comes back the HLQ exists. If not, you'll have to contact your site support group to define the HLQ on the receiving system.
And increasing the space from UI does NOT mean you have ruled out "Out of space or out of extents on the volume" -- you need to find out how much free space is on the volume and then verify the data set you are sending is smaller than the amount of free space on the volume. |
|
| Back to top |
|
|
|
|
