|
View previous topic :: View next topic
|
| Author |
Message |
swapnadeep.ganguly
Active User
Joined: 21 Mar 2007
Posts: 203
Location: India
|
|
|
|
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 |
|
 |
Devzee
Active Member
Joined: 20 Jan 2007
Posts: 684
Location: Hollywood
|
|
|
|
Continuation character is misssing..
| Code: |
SCIB009I SUBMITTED PROCESS NUMBER 00038370
SHORT TEXT => SSPA001I Submit process successful |
The PROC was submitted succesfully
If you are overriding this parameters, then you should have continuation chars - |
|
| Back to top |
|
|
swapnadeep.ganguly
Active User
Joined: 21 Mar 2007
Posts: 203
Location: India
|
|
|
|
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 |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix
|
|
|
|
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 |
|
|
Devzee
Active Member
Joined: 20 Jan 2007
Posts: 684
Location: Hollywood
|
|
|
|
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 |
|
|
swapnadeep.ganguly
Active User
Joined: 21 Mar 2007
Posts: 203
Location: India
|
|
|
|
| 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 |
|
|
Devzee
Active Member
Joined: 20 Jan 2007
Posts: 684
Location: Hollywood
|
|
|
|
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 |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix
|
|
|
|
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 |
|
|
swapnadeep.ganguly
Active User
Joined: 21 Mar 2007
Posts: 203
Location: India
|
|
|
|
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 |
|
|
swapnadeep.ganguly
Active User
Joined: 21 Mar 2007
Posts: 203
Location: India
|
|
|
|
Hi,
The issue is resolved after the continuation parameter is removed from the &OPDISP line. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix
|
|
|
|
Thank you for leting us know  |
|
| Back to top |
|
|
|
|
