IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Connect:Direct File Name Continuation Problem


IBM Mainframe Forums -> All Other Mainframe Topics
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
swapnadeep.ganguly

Active User


Joined: 21 Mar 2007
Posts: 203
Location: India

PostPosted: Tue Jan 22, 2008 11:23 am
Reply with quote

Hi All,

I am required to FTP files from Mainframes to UNIX server. But the output file path including the UNIX diretory is not accmodated in a single line. Can anyone please let me know the method in which we can continue to use the other line?

I am attaching the code that I am currently using for the output file:
Code:

SIGNON USERID=(Y) ESF=YES                                         
SUBMIT PROC=MODEL90X HOLD=NO CASE=YES                            -
   SNODE=UNIX.TCMINDU1.P                                         -
   &FROM=PNODE                                                   -
   &TO=SNODE                                                     -
   &COMPOPT=EXT                                                  -
   &OPDISP=(RPL)                                                 -
   &TRNODE=PNODE                                                 -
   &DSN01=XXXXXXXX.G3709W01.XXXX.REINGRP.DAT(0)                  -
   &OUT01='/datastage/data/CLMI_WHSE_DEV/Loss/src                -
           /XXXXXXX.G3709W01.XXXX.REINGRP.DAT                    -
   &BEGIN=STEP01                                                 
SIGNOFF


I have also tried the code by removing the continuation mark for the &OUT01 step. That piece of code is shown under:
Code:

SIGNON USERID=(Y) ESF=YES                                         
SUBMIT PROC=MODEL90X HOLD=NO CASE=YES                            -
   SNODE=UNIX.TCMINDU1.P                                         -
   &FROM=PNODE                                                   -
   &TO=SNODE                                                     -
   &COMPOPT=EXT                                                  -
   &OPDISP=(RPL)                                                 -
   &TRNODE=PNODE                                                 -
   &DSN01=XXXXXXXX.G3709W01.XXXX.REINGRP.DAT(0)                  -
   &OUT01='/datastage/data/CLMI_WHSE_DEV/Loss/src               
           /XXXXXXX.G3709W01.XXXX.REINGRP.DAT                    -
   &BEGIN=STEP01                                                 
SIGNOFF



Please let me know the exact procedure.[/code]
Back to top
View user's profile Send private message
superk

Global Moderator


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

PostPosted: Wed Jan 23, 2008 6:00 am
Reply with quote

I'd go with the same recommendation I made here in this previous topic.
Back to top
View user's profile Send private message
swapnadeep.ganguly

Active User


Joined: 21 Mar 2007
Posts: 203
Location: India

PostPosted: Fri Jan 25, 2008 1:14 pm
Reply with quote

Hi,

When I tried to use your solutions, I was not successful. In one case, the job abended with a abend message whereas in the other case, the job ended with a return code of 12. I am attaching the spool messages for both the conditions:

Cond1: I used the following piece of code:

Code:

SIGNON USERID=(Y) ESF=YES                                         
SUBMIT PROC=MODEL90X HOLD=NO CASE=YES                            -
   SNODE=UNIX.TCMINDU1.P                                         -
   &FROM=PNODE                                                   -
   &TO=SNODE                                                     -
   &COMPOPT=EXT                                                  -
   &OPDISP=(RPL)                                                 -
   &TRNODE=PNODE                                                 -
   &NOD1=\/datastage/data/CLMI_WHSE_DEV/Loss/src\                -
   &NOD2=\/XXXXXXXX.G3709W01.CLSI.REINGRP.DAT\                   -
   &FILE = &NOD1 || &NOD2                                        -
   &DSN01=XXXXXXXX.G3709W01.CLSI.REINCRTL.CTL(0)                 -
   &OUT01=&FILE                                                  -
   &BEGIN=STEP01                                                 -
   &CONDXNG=0                                                    -
   &TRNODXNG=PNODE                                               -
   &JCLIBXNG=XXXXXX.G3709.TEST1.SRUNJCL                          -
   &TRJOBXNG=G37092BT                                             
SIGNOFF                                                           


The message that was displayed in the NDM message region is as under:

Code:

LOCATE Failed: Entry not found in catalog.               
                                                         
The data set was being allocated OLD or SHR but the       
data set was not found.                                   
                                                         
SYSTEM ACTION:  The copy step ends in error with RC=8.   
                                                         
RESPONSE:  Issue a Select Statistics for the process     
including WTO records to verify the allocation string.   
Insure the data set receiving the LOCATE error exists and
is cataloged before resubmitting the process.             


Cond2: The Piece of code and the error message displayed is as under:
Code:

SIGNON USERID=(Y) ESF=YES                                         
SUBMIT PROC=MODEL90X HOLD=NO CASE=YES                            -
   SNODE=UNIX.TCMINDU1.P                                         -
   &FROM=PNODE                                                   -
   &TO=SNODE                                                     -
   &COMPOPT=EXT                                                  -
   &OPDISP=(RPL)                                                 -
   &TRNODE=PNODE                                                 -
   &DSN01=XXXXXXXX.G3709W01.CLSI.REINGRP.DAT(0)                  -
   &OUT01='/datastage/data/CLMI_WHSE_DEV/Loss/src                 
           /XXXXXXXX.G3709W01.CLSI.REINGRP.DAT'                  -
   &BEGIN=STEP01                                                 -
   &CONDXNG=0                                                    -
   &TRNODXNG=PNODE                                               -
   &JCLIBXNG=XXXXXX.G3709.TEST1.SRUNJCL                          -
   &TRJOBXNG=G37092AT                                             
SIGNOFF                                                           


The Error message as displayed in the spool is as under:
Code:

SCIB006I                                                                       
 SIGNON COMMAND (CONDENSED) => USERID /NODE =  XXXXXXX                           
XXXXXXX                                                                         
SCIC000I Connect:Direct - RC=00000000 MSG=SAFA000I NODE=CD2.XXXXXXXXX    @ 02:33
   SHORT TEXT => SAFA000I Connect:Direct SIGNON process completed.             
SCIC006I Parse error detected in command string.                               
SCIC011I                                                                       
 Errored string record began ==>  SUBMIT PROC=MODEL90X HOLD=NO CASE=YES  SNODE=U
   &COMPOPT=EXT   &OPDISP=(RPL)   &TRNODE=PNODE   &DSN01=XXXXXXXX.G3709W01.CLSI.
SCIB007I  COMMAND =>  SIGNOFF FORCED BY DMBATCH                                 
SCIC000I Connect:Direct - RC=00000000 MSG=SVTA003I NODE=CD2.XXXXXXXXX    @ 02:33
   SHORT TEXT => SVTA003I Interactive user has been logged off.                 


Please let me know where exactly am i going wrong in my understanding?
Back to top
View user's profile Send private message
swapnadeep.ganguly

Active User


Joined: 21 Mar 2007
Posts: 203
Location: India

PostPosted: Wed Jan 30, 2008 2:17 pm
Reply with quote

Hi All,

Please tell me why am I getting the Parse error as shown above? Its very urgent. Please suggest an alternate method for the problem.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Wed Jan 30, 2008 9:17 pm
Reply with quote

Hello,

Quote:
Its very urgent. Please suggest an alternate method for the problem.
If transferring the file is urgent you might use ftp until this is resolved.

Has the "data set not found" issue been resolved? Might the parse error be caused by the data set problem?
Back to top
View user's profile Send private message
superk

Global Moderator


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

PostPosted: Wed Jan 30, 2008 10:28 pm
Reply with quote

If it's really urgent, then hopefully during this time you've already opened an incident ticket with Sterling Commerce. My experience with them is that they usually react in a very reasonable amount of time to customer issues. At the very least, hopefully you've contacted your own Administrator to work out a feasible solution to your problem.

I have posted previously a possibility where you can use the Connect:Direct Process language's stringing and concatenation functions to string together a bunch of tokens into one contiguous string.
Back to top
View user's profile Send private message
swapnadeep.ganguly

Active User


Joined: 21 Mar 2007
Posts: 203
Location: India

PostPosted: Thu Jan 31, 2008 11:26 am
Reply with quote

Hi All,

The piece of code that worked for me is as under:
Code:

&OUT01=\'/datastage/data/XXXX_XXXX_XXX/Loss/src/\||           -   
        \XXXXXXXX.XXXXXXXX.XXXX.REINGRP.DAT'\                 -   
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> All Other Mainframe Topics

 


Similar Topics
Topic Forum Replies
No new posts Compare 2 files and retrive records f... DFSORT/ICETOOL 3
No new posts FTP VB File from Mainframe retaining ... JCL & VSAM 8
No new posts Extract the file name from another fi... DFSORT/ICETOOL 6
No new posts How to split large record length file... DFSORT/ICETOOL 10
No new posts Extracting Variable decimal numbers f... DFSORT/ICETOOL 17
Search our Forums:

Back to Top