Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Problem with NDM

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> All Other Mainframe Topics
View previous topic :: :: View next topic  
Author Message
preethan
Warnings : 1

New User


Joined: 15 Dec 2008
Posts: 33
Location: Chennai

PostPosted: Fri Dec 09, 2011 11:37 am    Post subject: Problem with NDM
Reply with quote

I have a problem with my NDM. I am trying to NDM a dataset present in region YYYYY to region XXXXX. I am trying to do with the help of jcl. When i submit the jcl from the region YYYYY, i am able to NDM the dataset. But when i do the vice versa (submitting the jcl from the region XXXXX and still trying to NDM the file from YYYYY to XXXXX), it is not NDM ing. Is there any possibility to do this ? I am developing a tool in the region XXXXX and the one of the aims of the tool is to NDM the files from YYYYY to XXXXX, without goin to the region YYYYY. I hope my question was clear.

The command which i used is

Code:
NDM       PROCESS PNODE=NDM.YYYYY           -
                            SNODE=NDM.XXXXX         -
&PDSN=AAAA.BBBB.CCCC        -
&SDSN=AAAA.BBBB.CCCC

STEP1     COPY TO   (DSN=&SDSN                -
                     DISP=NEW)                -
               FROM (DSN=&PDSN                -
                     DISP=SHR)
Back to top
View user's profile Send private message

vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1445
Location: Azeroth

PostPosted: Fri Dec 09, 2011 11:51 am    Post subject:
Reply with quote

Hi,
What is the error message you are getting?

The NDM job would have a process number for each transfer. You can note down this process number from the job and query it on NDM(user interface) to know what exactly is the issue.
Back to top
View user's profile Send private message
preethan
Warnings : 1

New User


Joined: 15 Dec 2008
Posts: 33
Location: Chennai

PostPosted: Fri Dec 09, 2011 12:11 pm    Post subject:
Reply with quote

***** ERROR ***** - This Node
NOTE: Unable to allocate dataset
From ( Pnode

I got this error from the NDM user interface. It is trying to allocate the dataset ? The datset will be present only in the other region from where I want this file to be copied. Is there any way to do that ? Should we always submit the NDM process only from the primary node ?
Back to top
View user's profile Send private message
vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1445
Location: Azeroth

PostPosted: Fri Dec 09, 2011 12:21 pm    Post subject:
Reply with quote

Hi,
Quote:
Should we always submit the NDM process only from the primary node ?

Im sure, transfer can be done in both ways, from both the nodes.

I don't know why the allocation failed, maybe if you could provide the complete error log of NDM, someone might be able to help you.

Just a guess,
If the error is with PNODE, then the dataset might have been in use by someother job or process.
If the error is with SNODE, you can try to manually allocate the dataset using 3.2 ISPF in SNODE and then try to receive with DISP=OLD
Back to top
View user's profile Send private message
Nic Clouston

Global Moderator


Joined: 10 May 2007
Posts: 1712
Location: UK

PostPosted: Fri Dec 09, 2011 4:45 pm    Post subject:
Reply with quote

You can always try and direct your job to run on the other system without logging on to it. You need a JES control card but I forget the syntax - something like
Code:
/* SYS=YYYYY
Back to top
View user's profile Send private message
PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2422
Location: Netherlands, Amstelveen

PostPosted: Fri Dec 09, 2011 4:54 pm    Post subject:
Reply with quote

Nic,

i think its something like this

/*ROUTE XEQ nodename
Back to top
View user's profile Send private message
Nic Clouston

Global Moderator


Joined: 10 May 2007
Posts: 1712
Location: UK

PostPosted: Fri Dec 09, 2011 5:49 pm    Post subject:
Reply with quote

That would be it - haven't seen it since 1989-ish hence the haziness.
Back to top
View user's profile Send private message
vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1445
Location: Azeroth

PostPosted: Fri Dec 09, 2011 5:54 pm    Post subject:
Reply with quote

I think Nic's memory corresponds to
/*JOBPARM SYSAFF=LPAR-ID
Back to top
View user's profile Send private message
Phrzby Phil

Active Member


Joined: 31 Oct 2006
Posts: 961
Location: Richmond, Virginia

PostPosted: Fri Dec 09, 2011 6:37 pm    Post subject:
Reply with quote

The NDM Select Statistics report also includes the error code. What does quick-weference say about that? (Sorry, I learned NDM at the Elmer Fudd Institute.)

You say the dataset should exist only on YYYYY - true - but to copy it to XXXXX the receiving dataset must be ALLOCATED on XXXXX.

Duplicate name on XXXXX?
Back to top
View user's profile Send private message
superk

Moderator Team Head


Joined: 26 Apr 2004
Posts: 4648
Location: Raleigh, NC, USA

PostPosted: Fri Dec 09, 2011 7:15 pm    Post subject: Reply to: Problem with NDM
Reply with quote

Let's go back and look at the Process. I think you need to be a bit clearer in your definition. You should identify which dataset is on which node. It appears that YYYY is considered the primary node, and XXXX the secondary node. On your COPY statement you should specify which node is FROM and which node is TO. My guess is that it should look something like:

Code:

NDM       PROCESS PNODE=NDM.YYYYY           -
                            SNODE=NDM.XXXXX         -
&PDSN=AAAA.BBBB.CCCC        -
&SDSN=AAAA.BBBB.CCCC

STEP1     COPY TO(SNODE DSN=&SDSN                -
                     DISP=(RPL,CATLG,DELETE))                -
               FROM(PNODE DSN=&PDSN                -
                     DISP=SHR)


Also, unless the SDSN dataset is a GDG and you're specifying a (+1) relative generation, I wouldn't use NEW.
Back to top
View user's profile Send private message
preethan
Warnings : 1

New User


Joined: 15 Dec 2008
Posts: 33
Location: Chennai

PostPosted: Tue Dec 13, 2011 5:21 pm    Post subject: Re: Reply to: Problem with NDM
Reply with quote

The copy keyword should be immediately followed by a left paranthesis. I got the above error while submitting the jcl.

I compared the statistics of the failed NDM through JCL and a successful NDM through the NDM user interface. There is only one difference.

In a well ran NDM it is like,

***** CHECKPOINTED; Interval => 10,240,000
From ( Snode
Dsn=>AAAA.BBBB.CCCC)
recs => 283 blks => 0
I/O BYTES => 150,556
VTAM BYTES => 151,688
Cmpr Perc => - 0.8%
Digital Signature enabled = No
To ( Pnode
Dsn=>AAAA.BBBB.CCCC)
recs => 283 blks => 0
I/O BYTES => 150,556
VTAM BYTES => 151,688
Cmpr Perc => - 0.8%
Digital Signature enabled = No
Merged Signature enabled = No
Merged Encryption enabled = No

In the NDM which failed the statistics is like below

***** ERROR ***** - This Node
NOTE: Unable to allocate dataset
From ( Pnode
Dsn=>AAAA.BBBB.CCCC)
recs => 0 blks => 0
I/O BYTES => 0
VTAM BYTES => 0
Cmpr Perc => 0.0%
Digital Signature enabled = No
To ( Snode
Dsn=>AAAA.BBBB.CCCC)
recs => 0 blks => 0
I/O BYTES => 0
VTAM BYTES => 0
Cmpr Perc => 0.0%
Digital Signature enabled = No
Merged Signature enabled = No
Merged Encryption enabled = No

I just learnt one difference. In my failed NDM the from node is considered as Primary NODE, whereas in a successfull NDM from node is considered as Secondary node. How can i specify that i need to copy from a secondary node ?. Any idea ?


superk wrote:
Let's go back and look at the Process. I think you need to be a bit clearer in your definition. You should identify which dataset is on which node. It appears that YYYY is considered the primary node, and XXXX the secondary node. On your COPY statement you should specify which node is FROM and which node is TO. My guess is that it should look something like:

Code:

NDM       PROCESS PNODE=NDM.YYYYY           -
                            SNODE=NDM.XXXXX         -
&PDSN=AAAA.BBBB.CCCC        -
&SDSN=AAAA.BBBB.CCCC

STEP1     COPY TO SNODE (DSN=&SDSN                -
                     DISP=NEW)                -
               FROM PNODE (DSN=&PDSN                -
                     DISP=SHR


Also, unless the SDSN dataset is a GDG and you're specifying a (+1) relative generation, I wouldn't use NEW.
Back to top
View user's profile Send private message
preethan
Warnings : 1

New User


Joined: 15 Dec 2008
Posts: 33
Location: Chennai

PostPosted: Tue Dec 13, 2011 8:38 pm    Post subject:
Reply with quote

It is working fine atlast!!

A small correction in the above command. It should be like

Code:
STEP1 COPY FROM (SNODE DSN='AAAA.BBBB.CCCC' -
DISP=SHR)-
TO (PNODE DSN='AAAA.BBBB.CCCC' -
DISP=(NEW,CATLG))


Thanks for all your help!!
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> All Other Mainframe Topics All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Problem in writing Output file vickey_dw COBOL Programming 5 Mon Nov 14, 2016 11:14 pm
No new posts Problem in Running Query via JCL vickey_dw DB2 3 Tue Oct 18, 2016 11:11 pm
No new posts DB2 Streaming Batch Processing Problem Manshadi DB2 4 Sat Sep 24, 2016 12:14 pm
No new posts Problem with GETMAIN command amitc23 CICS 6 Thu Sep 01, 2016 1:01 pm
No new posts TXT2PDF problem - printing @ in PDF vipul65 All Other Mainframe Topics 9 Thu Aug 25, 2016 12:48 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us