Good day
We have the following set up, but it will run successful for a few times, then suddely abend, but run successful again on a retry. It is not time related as we eliminated it already. Is there something we miss in the below?
On an abend I can see the following two things:
1. SEL STAT WHERE (STARTT = (01/09/2012,05:22:02) STOPT = (01/09/2012,05:42:35) CCODE = (NE,0) PNUM = 46919 TYPE = (CT RT RJ PT)) FILE.
2. SCIB022I CACS2LAW (00046919) STEP3 00000001/XSMG402I
SCIB022I CACS2LAW (00046919) 00000001/SVTM100I
The SVTM100I error is regarding TCQ deletion and I think it might be the problem, but I do not know how to fix it..
CACS2LAW PROCESS
SYMBOL &OFILE=\'\ ||
&TODSN || _ || &DATE ||
\'\
*
SYMBOL &RUN1=\'\scp -p || \ \ || / ||
&DIRA || / || &DIRB || / ||
&DIRC || / || &DIRD || / || &DIRE || / || &TODSN || _ ||
&DATE || \ \ ||
&VAR1 || / || &DIR1 || / || &DIR2 || / || &TODSN || _ ||
&DATE ||
\'\
*
SYMBOL &RUN2=\'\ssh || \ \ ||
&VAR2 || \ \ || / || &DIR1 || / || &DIR2 || / ||
&SCRPT || \ \ || &TODSN || _ || &DATE ||
\'\
*
STEP1 COPY FROM (DSN=&FRDSN DISP=&FRDISP)
&COMP
TO (DSN=&OFILE DISP=&TODISP
SYSOPTS=":datatype=text:")
*
IF (STEP1 > 0) THEN
GOTO STEP4
ELSE
*
STEP2 RUN TASK SNODE (PGM=UNIX)
SYSOPTS=&RUN1
*
STEP3 RUN TASK SNODE (PGM=UNIX)
SYSOPTS=&RUN2
EIF
*
IF (STEP1 GT 0) THEN
STEP4 RUN TASK PNODE (PGM=DMNOTIFY,PARM=(CL4'FAIL','&FRDSN'))
EIF
Thanks
Connect Direct
-
- Global moderator
- Posts: 3006
- Joined: Fri Apr 18, 2008 11:25 pm
- Skillset: tso,rexx,assembler,pl/i,storage,mvs,os/390,z/os,
- Referer: www.ibmmainframes.com
Re: Connect Direct
and what does the issue have in common with COBOL ? 

cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort
-
- Global moderator
- Posts: 3720
- Joined: Sat Dec 19, 2009 8:32 pm
- Skillset: Systems programming, SAS, COBOL, CICS, JCL, SMS, VSAM, etc.
- Referer: other forum
- Location: Dubuque, Iowa, USA
Re: Connect Direct
What did the vendor support personnel tell you when you asked the question of them?
Topic moved since not COBOL related in any way.
Topic moved since not COBOL related in any way.
- dick scherrer
- Global moderator
- Posts: 6268
- Joined: Sat Jun 09, 2007 8:58 am
Re: Connect Direct
Hello and welcome to the forum,
Is TCQ a typo? I'm not familiar with this tca (3 char abbrev).
Is there something to be sent? If all is sent, the error may be due to "nothing to send".
As XSMG402I is issued first, what causes this message?
Is TCQ a typo? I'm not familiar with this tca (3 char abbrev).
Is there something to be sent? If all is sent, the error may be due to "nothing to send".
As XSMG402I is issued first, what causes this message?
Hope this helps,
d.sch.
d.sch.
Re: Connect Direct
Robert: the vendor support was not much help. They 'investigate', but then you don't hear from them again. Thanks for moving the topic.
Dick: TCQ stands for Transmission Control Queue (TCQ). There are 2 files to be send thus STEP2 & STEP3 (the way I understand it). When the job run successfull there are no XSMG401I, but a SVTM118I. On an abend it seems like XSMG402I is issued on the first try (?) but then it seems like it is trying to do something again and then we end up with the SVTM100I to say the process on the TCQ has been deleted. I think this is the logic behind it, but I don't know what and where to fix not to end up with an abend every second day. If we rerun the job again it goes through, but I would like to have an automated retry rather then get called for it.
Dick: TCQ stands for Transmission Control Queue (TCQ). There are 2 files to be send thus STEP2 & STEP3 (the way I understand it). When the job run successfull there are no XSMG401I, but a SVTM118I. On an abend it seems like XSMG402I is issued on the first try (?) but then it seems like it is trying to do something again and then we end up with the SVTM100I to say the process on the TCQ has been deleted. I think this is the logic behind it, but I don't know what and where to fix not to end up with an abend every second day. If we rerun the job again it goes through, but I would like to have an automated retry rather then get called for it.
- dick scherrer
- Global moderator
- Posts: 6268
- Joined: Sat Jun 09, 2007 8:58 am
Re: Connect Direct
Hello,
It sounds as though there is some process-specific setup or housecleaning that is leaving things "hanging". I've seen many NDM/ConnectDirect topics on several forums and do not recall a situation where the process does a "flip-flop" on alternating runs.
Understood, but what causes a XSMG402I to be issued?On an abend it seems like XSMG402I is issued on the first try (?)
It sounds as though there is some process-specific setup or housecleaning that is leaving things "hanging". I've seen many NDM/ConnectDirect topics on several forums and do not recall a situation where the process does a "flip-flop" on alternating runs.
Hope this helps,
d.sch.
d.sch.
Re: Connect Direct
This is the order and meaning of the codes in the output:
SVTM118I DMPRCMGR Process Execution Status being passed to Synch Submit request. The Process status is reflected in the return code. This is the highest value for all Process steps. A non-zero value means at least one step in the Process failed. Complete statistics for this Process are available via the SEL STAT command. RC=52(x'34') indicates that MAXDELAY=0 was specified and the process did not run and was deleted. SYSTEM ACTION: Processing continues. RESPONSE: You may view the current Process status by using the SELECT STATISTICS command unless RC=52(x'34').
Regarding the above: RC000001 and: SEL STAT WHERE (STARTT = (01/09/2012,05:22:02) STOPT = (01/09/2012,05:42:35) CCODE = (NE,0) PNUM = 46919 TYPE = (CT RT RJ PT)) FILE.
XSMG402I - A user RUNTASK step completed. A RUNTASK step was completed in the user process (the user task was executed).Check the return code for user task status. SYSTEM ACTION: Normal C:D execution continues. RESPONSE: None.
SVTM100I DMSESMGR PROCESS TERMINATED. ALL PROCESSING FOR THE PROCESS HAS ENDED. THE HIGHEST RETURN CODE IS DISPLAYED. SYSTEM ACTION: THE PROCESS IS DELETED FROM THE TCQ. RESPONSE: NONE.
Thanks.
SVTM118I DMPRCMGR Process Execution Status being passed to Synch Submit request. The Process status is reflected in the return code. This is the highest value for all Process steps. A non-zero value means at least one step in the Process failed. Complete statistics for this Process are available via the SEL STAT command. RC=52(x'34') indicates that MAXDELAY=0 was specified and the process did not run and was deleted. SYSTEM ACTION: Processing continues. RESPONSE: You may view the current Process status by using the SELECT STATISTICS command unless RC=52(x'34').
Regarding the above: RC000001 and: SEL STAT WHERE (STARTT = (01/09/2012,05:22:02) STOPT = (01/09/2012,05:42:35) CCODE = (NE,0) PNUM = 46919 TYPE = (CT RT RJ PT)) FILE.
XSMG402I - A user RUNTASK step completed. A RUNTASK step was completed in the user process (the user task was executed).Check the return code for user task status. SYSTEM ACTION: Normal C:D execution continues. RESPONSE: None.
SVTM100I DMSESMGR PROCESS TERMINATED. ALL PROCESSING FOR THE PROCESS HAS ENDED. THE HIGHEST RETURN CODE IS DISPLAYED. SYSTEM ACTION: THE PROCESS IS DELETED FROM THE TCQ. RESPONSE: NONE.
Thanks.
-
- Similar Topics
- Replies
- Views
- Last post
-
-
Transfering ASCII files to z/OS USS using Connect Direct
by golemis » Sun Feb 21, 2021 2:24 pm » in All other Mainframe Topics - 1
- 6832
-
by golemis
View the latest post
Mon Feb 22, 2021 6:32 pm
-