Any way to find the success of NDM

kratos86 · Posted: Fri Jul 04, 2008 10:58 am

Is there any case like - the NDM job is submitted and its RC = 00. But the file is not transmitted successfully. In this case is there anything that we can do. To check the file is transmitted. Like any additional step, that can be added to find this out.

regards,
raj

HappySrinu · Active User Joined: 22 Jan 2008 Posts: 194 Location: India

can't you go and check on target lpar/machine regarding that transferring dataset

secondly if you are in foreground, you can use option "SS" for completed process

kratos86 · Posted: Fri Jul 04, 2008 2:27 pm

Hi Srini,
We have various NDM jobs running in late nights. So, it is not possible for us to sit and monitor the jobs always. And also we have authentication only to send files to the LPAR.

whenever a ndm fails it will give a non-zero return code. We get page regarding that.

As i mentioned, Is there any way to find out ...

regards,
Raj

superk · Posted: Fri Jul 04, 2008 3:44 pm

Raj, I'm confused.

First, you said that you want to know when a Process has executed successfully. Srini gave the correct answer. You, or an authorized person, should use the Select Statistics (SS) option from the Connect:Direct User Interface (on CICS or on ISPF) to determine the status of your Process.

Next, you say that some of these run late at night and it's not possible to be there to monitor them. You also say that whenever a Process fails you get a page. So, if you're not there to monitor the Processes, what do you want done? Surely you must have onsite operations and product support teams who would perform that function on your behalf? Don't you post alerts to your operator consoles if a Process fails? Wouldn't they then page out to your team?

The problem I have here is that I don't know what your policies and procedures are regarding these Processes.

My first thought is that you should change your procedures to have your Connect:Direct jobs submit the Process, then sit and wait for your Process to complete. If the process completes successfully, then your job ends. If it fails, then your job abends or ends with a non-zero RC, whichever is preferred in your shop.

My second thought is that you should include steps in your Process code to check the RC of the COPY step and take an appropriate course of action if it is not zero, such as sending a message to your terminal or a console, sending an email, calling some other program or batch job to perform some other type of action.

My third thought is that you would have another job that would run after your Process has completed that would run a batch equivalent of the formerly mentioned SS report.

kratos86 · Posted: Tue Jul 08, 2008 9:52 am

Hi kevin,

unni_nss · New User Joined: 20 Sep 2005 Posts: 19

In the case of NDM jobs, RC = 0, doesnt mean that file has been transmitted successfully. you need to check with the process no from your NDM sysout step.

kratos86 · Posted: Tue Jul 08, 2008 2:46 pm

Hi unni_nss,

superk · Posted: Tue Jul 08, 2008 3:07 pm

The Connect:Direct User's Guide gives the details for the syntax of the SELECT STATISTICS command.

arun prazad · New User Joined: 13 Dec 2007 Posts: 2 Location: India

Hi,

I am continuing an old post because my requirement is also the same as what kratos86 asked and I didn't see it being answered.

I would like to know is there any way to know whether the file has been transmitted successfully from the job. In some cases the The NDM job ( JCL ) gives a return code zero and the file is not transmitted. We can get the details by looking at SELECT STATISTICS. I would like to know if there is any way to handle this in JCL ,meaning if the process return code is non-zero I need to abend step in JCL. In other words is there any way to capture the process return code from JCL.

Thanks in advance
Prasad

superk · Posted: Tue Aug 19, 2008 7:27 pm

Raj & Prased, what are your respective site's policies on using either the CDWAIT/CDPOST or MAXDELAY parameters for your processes?

arun prazad · New User Joined: 13 Dec 2007 Posts: 2 Location: India

Kevin,

I am not sure of where to check for these parameters ( CDWAIT/CDPOST or MAXDELAY ). If I code MAXDELAY=UNLIMITED will it solve my issue. nothing is coded in the control card or in side the proc which we submit thru the control card. How can I know what is the value for this? is there any default value for this? can you please share with us about the parameters CDWAIT and CDPOST.

A big thanks to you for taking me to the right path
Regards
Prasad

superk · Posted: Thu Aug 21, 2008 1:34 am

I'd really like to see you follow-up on these parameters from the appropriate documents.

From the Connect:Direct for z/OS (Version 4.7) User's Guide section titled Synchronizing Submitted Processes:

Steve Elliott · Posted: Wed Mar 04, 2009 11:34 am

We use CDWAIT to process file transfers, and then use CDPOST within the CD PROC to pass a return code back from the file transfer to the mainframe job.

A sample PROC would look like this:

COPYSND COPY -
FROM . . . . -
TO . . . .

IF (COPYSND NE 0) THEN
POSTBAD1 RUN TASK (PGM=CDPOST -
PARM=(XL4'&ASCB' XL4'&ECB' F'8')) PNODE
ELSE
POSTGOOD RUN TASK (PGM=CDPOST -
PARM=(XL4'&ASCB' XL4'&ECB' F'0')) PNODE
EIF

This means that when the copy fails the CDWAIT step completes with a return code of 8 (from the F'8')

You can also use this logic to place a RUN TASK, within the IF statement, so that it only runs if the transfer was successful.
See below.

COPYSND COPY -
FROM . . . . -
TO . . . .

IF (COPYSND NE 0) THEN
POSTBAD1 RUN TASK (PGM=CDPOST -
PARM=(XL4'&ASCB' XL4'&ECB' F'8')) PNODE
ELSE
RUNSTEP1 RUN TASK . . . .

IF (RUNSTEP1 NE 0) THEN
POSTBAD RUN TASK (PGM=CDPOST -
PARM=(XL4'&ASCB' XL4'&ECB' F'4')) PNODE
ELSE
POSTGOOD RUN TASK (PGM=CDPOST -
PARM=(XL4'&ASCB' XL4'&ECB' F'0')) PNODE
EIF
EIF

Here the rc will be 8 if the transfer fails, and 4 if the run task fails.

Richa.K · New User Joined: 23 Dec 2009 Posts: 3 Location: Pune

With respect to the information you all have provided, as to use MAXDELAY=UNLIMITED.But this didn't work in our job.
Please find below the code and let me know if I am wrong anywhere ;

SIGNON ESF=YES
SUBMIT PROC=SWBPAGE MAXDELAY=UNLIMITED -
HOLD=NO -
&NDMID=JS4654 -
&NODE=PNODE -
SNODE=TCPNAME=150.233.141.180 -
&DSN1=CPMC.BR33011A.UPDTFILE(0) -
&DSN2='CSQDAILY\MIDWESTTELCOH1C' -
&DISP2=(NEW,CATLG,DELETE) -
&COMPRESS=COMPRESS
SIGNOFF

While using the above code, our job is takes much time as its average time is of 1 min.

Please let me know if anyone can help me over this.

enrico-sorichetti · Posted: Mon Jan 18, 2010 4:38 pm

Richa.K · New User Joined: 23 Dec 2009 Posts: 3 Location: Pune

We want our process to complete in same time, and if NDM fails then it should drop an email.

But the problem is that the process is not getting complete when we use MAXDELAY=UNLIMITED and every time we have to cancel and manually send the file to the target destination.

Richa.K · New User Joined: 23 Dec 2009 Posts: 3 Location: Pune

Adding to the above, when we ran test for using MAXDELAY it worked fine,but in production it shows that" process is not completed while the job is running from last 30 mins

thanks.