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
 

 

Connect Direct to transfer a file from mainframe to Unix

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

Active User


Joined: 21 Mar 2007
Posts: 203
Location: India

PostPosted: Thu Oct 04, 2007 9:36 am    Post subject: Connect Direct to transfer a file from mainframe to Unix
Reply with quote

Hi,
I am required to transfer a file from mainframe database to Unix database. For that purpose, its essential to use the Connect Direct Method of file transfer. For that I am using the following PARM:

Code:

SIGNON USERID=(Y) ESF=YES                                         
SUBMIT PROC=MODEL90 SNODE=UNIX.TCMINDU1.P HOLD=NO CASE=YES     - 
   SNODEID=(USERID,PASSWORD)                                   
   &FROM=PNODE                                                   
   &TO=SNODE                                                     
   &DSN01=PV5240A.DB2.CARR.MKT.DTL                                 
   &OUT01='/DATASTAGE/DATA/CLSI_REQMNT/LOSSDB/CARRTST.DAT'- 
   &OPDISP=(RPL)                                                 
SIGNOFF       
                                                   


But using the above, I am getting a return code of 8. When i checked in the spool, I found the following error message:

Code:


SCIB006I                                                                       
 SIGNON COMMAND (CONDENSED) => USERID /NODE =  N48FF9                           
AVELERS                                                                         
SCIC000I Connect:Direct - RC=00000000 MSG=SAFA000I NODE=CD2.TRAVELERS    @ 23:52
   SHORT TEXT => SAFA000I Connect:Direct SIGNON process completed.             
SCIB007I  COMMAND =>  SUBMIT PROC=MODEL90 SNODE=UNIX.TCMINDU1.P HOLD=NO CASE=YES
SCIC000I Connect:Direct - RC=00000000 MSG=SSPA001I NODE=CD2.TRAVELERS    @ 23:52
SCIB009I SUBMITTED PROCESS NUMBER 00038370                                     
   SHORT TEXT => SSPA001I Submit process successful                             
SCIB007I  COMMAND =>   &FROM=PNODE                                             
SCIC000I Connect:Direct - RC=00000008 MSG=SCIA001I NODE=CD2.TRAVELERS    @ 23:52
   SHORT TEXT => SCIA001I Invalid C:D command.                                 
    LONG TEXT => The requested command is not supported by C:D. The command may
                 be missing or misspelled. Ensure that the command keyword is   
                 entered after column 1. Entries beginning in column 1 are     
                 treated as step names.                                         


Can any one please help me out to remove the error.
Back to top
View user's profile Send private message

Devzee

Active Member


Joined: 20 Jan 2007
Posts: 684
Location: Hollywood

PostPosted: Thu Oct 04, 2007 9:50 am    Post subject:
Reply with quote

Continuation character is misssing..

Code:
SCIB009I SUBMITTED PROCESS NUMBER 00038370                                     
   SHORT TEXT => SSPA001I Submit process successful

The PROC was submitted succesfully

Code:
&FROM=PNODE             

If you are overriding this parameters, then you should have continuation chars -
Back to top
View user's profile Send private message
swapnadeep.ganguly

Active User


Joined: 21 Mar 2007
Posts: 203
Location: India

PostPosted: Thu Oct 04, 2007 10:44 am    Post subject:
Reply with quote

Thank you Devzee.

The solution provided by you worked.

One more thing, the job ran successfully and ended with MAXCC=0. But when I tried to locate the file in the UNIX server, I was not able to find the same there.
Back to top
View user's profile Send private message
dick scherrer

Site Director


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

PostPosted: Thu Oct 04, 2007 11:59 am    Post subject:
Reply with quote

Hello,

A couple of questions. . .

Has anyone searched the unix file system for any file named CARRTST.DAT (the "new" path/file may have gotten hung off of other than the root directory)? If this is a file name already used in multiple places, change the file name to something that cannot already exist and try again.

Is it possible that the intended unix system is not where the transfer is being sent? Once upon a time, i worked in an environment where there were several unix servers and they had very similar names and ip addresses. Also, many of the same users had accounts on multiple systems.
Back to top
View user's profile Send private message
Devzee

Active Member


Joined: 20 Jan 2007
Posts: 684
Location: Hollywood

PostPosted: Thu Oct 04, 2007 12:03 pm    Post subject:
Reply with quote

JCL MAXCC=0 doesnt make sense in case of NDM transfers.

You need to look at the NDM log or take the NDM process number and check the statistics of the file transfer.
Also you can go to Unix box, and see the NDM log whether the file arrived on the Unix box.
Back to top
View user's profile Send private message
swapnadeep.ganguly

Active User


Joined: 21 Mar 2007
Posts: 203
Location: India

PostPosted: Thu Oct 04, 2007 12:19 pm    Post subject:
Reply with quote

One more thing, I am completely new to the UNIX system. Can anyone please help me out by letting me know of some documents which i can have a glance at?
Back to top
View user's profile Send private message
Devzee

Active Member


Joined: 20 Jan 2007
Posts: 684
Location: Hollywood

PostPosted: Thu Oct 04, 2007 12:23 pm    Post subject:
Reply with quote

Do search on web you will get some info.

Just by doing one file transfer you dont have to worry about getting UNIX system documentation and trying to find out what happened.
Just ask the person who receives or process this file on UNIX whether the file was received succesfully on UNIX. I'm not stopping you to learn Unix.
Back to top
View user's profile Send private message
dick scherrer

Site Director


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

PostPosted: Thu Oct 04, 2007 12:27 pm    Post subject:
Reply with quote

Hello,

Which unix operating environment (i.e HP, Sun, IBM, etc)? Once you know which op system, you'll want to know which "shell" you will normally be working with.

As this forum is geared for mainframe topics, we do not have any unix info as part of the forum.

I'd suggest looking on the web for some intro material. Once upon a time there was a book called "UNIX in a nutshell". It has gone thru multiple editions. Here's a link to O'Reilly:
http://www.oreilly.com/catalog/unixnut4/
Back to top
View user's profile Send private message
swapnadeep.ganguly

Active User


Joined: 21 Mar 2007
Posts: 203
Location: India

PostPosted: Tue Nov 13, 2007 1:02 pm    Post subject:
Reply with quote

Hi,

I am having a problem again regarding Connect Direct. For that reason I am re opening the topic.

The message as I can see in the spool is as under:
Code:

SCIC000I Connect:Direct - RC=00000008 MSG=SCBI003I NODE=CD2.XXXXXXXXX    @ 02:25
   SHORT TEXT => SCBI003I Invalid keyword found in SUBmit command.             
      UIERRM1 =>  SUBMIT  SIGNOFF     L#=      0                               
    LONG TEXT => There are two ways to issue the SUBmit command.  One is       
                 from within the process, the other is not.  When using         
                 the SUBmit command OUTSIDE the process the keyword 'PROC'     
                 or 'DSN' must be specified. Other valid optional command       
                 keywords:'HOLD', 'NEWNAME', 'PNODE', 'PRTY', 'RETAIN',         
                 'SNODE', 'CLASS', 'STARTT', and symbolic parameter values     
                 (designated by '&' as a prefix). Only when a SUBMIT is         
                 issued within a process is the 'SUBNODE' keyword valid.       
                 However, the 'PROC' and 'PNODE' keywords are NOT valid         
                 in this type of a SUBMIT.                                     
                 SYSTEM ACTION: Return to invoker with RC=8.                   
                 RESPONSE: Reenter your SUBmit command.                         
SCIB007I  COMMAND =>  SIGNOFF FORCED BY DMBATCH                                 
SCIC000I Connect:Direct - RC=00000000 MSG=SVTA003I NODE=CD2.XXXXXXXXX    @ 02:25
   SHORT TEXT => SVTA003I Interactive user has been logged off.                 


The code which i am using is as under:

Code:


SIGNON USERID=(Y) ESF=YES                                         
SUBMIT PROC=MODEL90 SNODE=UNIX.TCMINDU1.P HOLD=NO CASE=YES     - 
   SNODEID=(Userid,Password)                                   - 
   &DSN01=XXXXXXXX.GW01.CLSI.SPECIAL.CODE.DTL                  - 
   &OUT01='/datastage/data/CLMI_WHSE_DEV/Loss/src/SPECODE.DAT' - 
   &BEGIN=STEP01                                               - 
   &OPDISP=(RPL)                                               - 
SIGNOFF


Back to top
View user's profile Send private message
swapnadeep.ganguly

Active User


Joined: 21 Mar 2007
Posts: 203
Location: India

PostPosted: Tue Nov 13, 2007 2:06 pm    Post subject:
Reply with quote

Hi,

The issue is resolved after the continuation parameter is removed from the &OPDISP line.
Back to top
View user's profile Send private message
dick scherrer

Site Director


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

PostPosted: Tue Nov 13, 2007 8:14 pm    Post subject: Reply to: Connect Direct to transfer a file from mainframe t
Reply with quote

Thank you for leting us know icon_smile.gif
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 Converting Variable block file to Fix... bhavana yalavarthi DFSORT/ICETOOL 10 Tue May 16, 2017 2:20 pm
No new posts Getting error while opening a variabl... apandey1 COBOL Programming 5 Fri May 05, 2017 12:22 pm
No new posts Issue with NDM process to transmit ES... chetanambi All Other Mainframe Topics 6 Wed May 03, 2017 10:52 am
No new posts File processing vishwakotin Mainframe Interview Questions 9 Fri Apr 28, 2017 11:38 am
No new posts Occurrence of various strings within ... TS70363 JCL & VSAM 1 Thu Apr 27, 2017 8:18 pm


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