Connect Direct Error Code 2
Contents |
Technote (troubleshooting) Problem(Abstract) You receive these errors
Connect Direct Error Messages
with Connect:Direct for UNIX: XCPS007I XCPS002 Symptom XCPS002I Error: Source sun direct error code file open failed. Errno=&FDBK. Filename=&FILE. XCPS007I Error: Error communicating with user exit program. Error: sun direct error code e52-32 Error communicating between Connect:Direct and user exit program due to an internal error, or due to a problem in the user exit program.
Sun Direct Error Code E48-32
XCPS002I Source file open failed. Errno=2. Filename=Source_filename. Cause Miscoded parameters in /d_dir/ndm/cfg/node_name/userfile.cfg Connect:Direct for UNIX made a system call to open the source file coded in the Direct Process and UNIX could not open the file. UNIX returned a code (2) which is a "Bad filename
Source File Open Failed. Errno=2.
or directory". The source file name was coded incorrectly. Resolving the problem If the user ID running the Process is not restricted to an upload directory by setting the "pstmt.upload_dir" parameter to a directory name in the Userfile.cfg, the Process MUST have the source filename coded with the absolute pathname. If the user ID is restricted to an upload directory by defining a directory name in the pstmt.upload/download_dir parameter, a filename or a filename relative to the upload or download directory must be defined. Historical Number PRI196 Document information More support for: Sterling Connect:Enterprise for UNIX Software version: 2.4, 2.5 Operating system(s): AIX, HP-UX, Linux, Solaris Reference #: 1546070 Modified date: 2012-07-30 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
STERLINGPRI Technote (FAQ) Question How do I check the UNIX return code from Connect:Direct shell script? Answer Check the $? variable. Use a command like this immediately after the ndm error codes EOF of the "here document": x=$? However be aware that Connect:Direct for UNIX reinterprets
Source File Open Failed. Errno=&fdbk. Filename=&file
return codes to fit a particular scheme. Connect:Direct can issue return codes of 0, 4, 8 and 16 to represent good, ndm error code 8 warning, error and catastrophic error, respectively. Thus, return codes from run tasks will be re-interpreted to fit that scheme. Run task completion codes will generate the $? variable as follows: Completion code <=4, then http://www-01.ibm.com/support/docview.wss?uid=swg21546070 $? will yield 0 Completion code > 4, then $? will yield 8 For UNIX run task scripts that generate a Completion Code (CC) of 4 or less, you must perform additional tasks to make the $? non-zero. In the Connect:Direct Process after the run task, add an "if" step that checks the CC of the run task step. If the return code is 4 or less, program http://www-01.ibm.com/support/docview.wss?uid=swg21547989 it to execute another run task script on the PNODE that only has a statement of exit 5. Then the $? Variable is set to 8 when exiting the Connect:Direct part of the UNIX script. EXAMPLE #running this script will generate a $? Of 8 /cdunix/ndm/bin/direct -x << EOJ submit maxdelay=00:00:30 proc1 process snode=l1aix1.cd.v3301 step01 run task snode sysopts="/home/acme1/scrpt" step01a if (step01 lt 5) then step02 run task snode sysopts="/home/acme1/setcc" eif PEND; EOJ x=$? echo $x Here is an example of the results of running these example scripts: $ more scrpt exit 2 $ more setcc exit 5 The return code for a process is stored in the $? variable within the ksh or sh if the maxdelay=hh:mm:ss parameter is in the process. The maxdelay paramter is designed to force the submit command to wait until the process has completed or the assigned time has expired before returning control back to the shell. Additionally it stores the rc of a process in the $? variable for the ksh and sh. Below is a script that echos the rc for a process back to STDOUT #!/bin/sh # # This script invokes the Connect:Direct for UNIX CLI # and submits a process inline to copy
Technote (troubleshooting) http://www-01.ibm.com/support/docview.wss?uid=swg21523228 Problem(Abstract) CONNECT:Direct UNIX Runtask/Runjob Not Executing (SCI19129) Symptom Error: Retrun Code 127 Error: XSMG402I A user RUNTASK step completed. Error: http://www.unix.com/red-hat/174325-ibm-connect-direct-error.html Return code7F Restricted Shell Cause has specified a directory value in the pstmt.run_dir parm in the userfile.cfg file. Resolving error code the problem 1) When specifying a directory value in the pstmt.run_dir parm, this will causethe UNIX restricted shell to be invoked, providing enhanced security. If thisis preferred, the customer must understand the concepts of restricted shell environments and usage. Please direct error code review the CONNECT:Direct for UNIX Administration (Maintaining theUser Authorization Information File) for further details on the limitationsand usage when using CONNECT:Direct for UNIX.2) The customer may remove the directory which will remove the restriction andallow the customer to use the command. If no program directory is notspecified, the regualar (Bourne) shell is invoked for executing commands. Historical Number PRI338 Product Alias/Synonym Fact CONNECT:Direct for UNIX all versions SCI19129 Document information More support for: Sterling Connect:Enterprise for UNIX Software version: All Operating system(s): Platform Independent Reference #: 1523228 Modified date: 2012-07-30 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
open source technology solutions provider with offerings including Red Hat Enterprise Linux (RHEL), Fedora, open source applications, security and systems management, virtualization, and Services Oriented Architecture (SOA) solutions. Search Forums Show Threads Show Posts Tag Search Advanced Search Unanswered Threads Find All Thanked Posts Go to Page... linux operating commands and unix operating commands IBM Connect:Direct Error Red Hat Thread Tools Search this Thread Display Modes #1 01-04-2012 f.vietti Registered User Join Date: Jan 2012 Last Activity: 16 April 2012, 10:49 AM EDT Posts: 2 Thanks: 0 Thanked 0 Times in 0 Posts IBM Connect:Direct Error Hi to all, I've installed IBM Connectirect 4.1.00 on Red Hat Enterprise Linux Server release 5.5, but when I try to execute the "direct cli", I obtain the following error: [cduser@XXXXXXXXX bin]$ ./direct *********************************************************** * * * Licensed Materials - Property of IBM * * * * IBM(R) Sterling Connectirect(R) for UNIX 4.1.00 * * * * (C) Copyright IBM Corp. 1992, 2011 All Rights Reserved. * * * *********************************************************** Failed to obtain connection to Connectirect server, exiting. XSEC012I Return Code: 8 Feedback: 0 XAPI006I Return Code: 8 Feedback: 0 Command Line Interface network channel lost. Connectirect CLI Terminated... Any Idea? Remove advertisements Sponsored Links f.vietti View Public Profile Find all posts by f.vietti #2 01-04-2012 toro95037 Registered User Join Date: Sep 2010 Last Activity: 12 November 2012, 11:15 PM EST Posts: 17 Thanks: 0 Thanked 3 Times in 3 Posts IBM product documentation for Sterling Connect : Direct ... IBM Sterling Connectirect for UNIX Documentation - United States Sterling Connect : Direct for UNIX Getting Started Guide... ftp://public.dhe.ibm.com/software/co...ingStarted.pdf Sterling Connect : Direct for UNIX User Guide... ftp://public.dhe.ibm.com/software/co..._UserGuide.pdf I'd first look to see if you have the environmental variables set up correctly as outlined in the user's guide. Remove advertisements Sponsored Links toro95037 View Public Profile Find all posts by toro95037 #3 01-05-2012 f.vietti Registered User Join Date: Jan 2012 Last Activity: 16 April 2012, 10:49 AM EDT