Command Returned Error Code 65280
Contents |
here for a quick overview of the site Help Center Detailed answers to exit code 65280 in unix any questions you might have Meta Discuss the workings and policies exit code 65280 linux of this site About Us Learn more about Stack Overflow the company Business Learn more exit code 65280 in informatica about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack
Error Code 65280 In Unix
Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Perl system() call failed with return code 65280 up vote 2 down vote favorite I the code below, I can run $retCode = ClearCase($cmd); with no error, but error code 65280 in informatica return 65280 when run this: $retCode = ClearCase($logcmd); I tried on XP and Windows 2003 server, same result, all with ActiveState Perl v5.14.2. This code was working 2 years ago somewhere else. Thanks Jirong $g_HPPC_DEV_DRIVE = "M"; $g_HPPC_DEV_VIEW = "bldforge_AOMS_DEV"; $g_logfile = "logfile.txt"; $cmd = "startview $g_HPPC_DEV_VIEW"; $logcmd = $cmd . " >> $g_logfile 2>>&1"; $targetDir = $g_HPPC_DEV_DRIVE . ":\\" . $g_HPPC_DEV_VIEW; print "\$targetDir = $targetDir\n"; print "Starting view .......\n"; #$retCode = system("cleartool startview bldforge_AOMS_DEV >> logfile.txt"); #$retCode = `cleartool startview bldforge_AOMS_DEV`; $retCode = ClearCase($logcmd); #$retCode = ClearCase($cmd); sub ClearCase { my $retCode = 0; my $args = $_[0]; my $cmd = "cleartool " . $args; $retCode = Execute($cmd); return $retCode; } sub Execute { my $retCode = 0; my $cmd = $_[0]; if ($g_HPPC_BUILD_SIMULATION ne "Y") { print("Execute() Running...: $cmd\n"); $retCode = system($cmd); #$retOut = `$cmd`; #$retCode = $?; #print("Command execute output: $retOut\n"); } else { print("Execute() *** SIMULATION: $cmd\n"); } print("Execut
van GoogleInloggenVerborgen veldenZoeken naar groepen of berichten
Plans & Pricing Partners Support Resources Preview Forums Forums Quick Links Search Forums New Posts Search https://forums.cpanel.net/threads/system-failed-with-exit-code-65280.328371/ titles only Posted by Member: Separate names with a comma. Newer Than: Search this thread only Search this forum only Display results as threads More... Useful Searches http://www-01.ibm.com/support/docview.wss?uid=isg1OA47398 Recent Posts Resources Resources Quick Links Search Resources Most Active Authors Latest Reviews Feature Requests Defects Menu Log in Sign up The Community Forums Interact with code 65280 an entire community of cPanel & WHM users! cPanel Forums > cPanel & WHM® (for Linux® Servers) > EasyApache > This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More. system' failed with exit code '65280' !! Discussion in 'EasyApache' started by code 65280 in dragon2611, Mar 6, 2013. dragon2611 Well-Known Member Joined: Nov 30, 2003 Messages: 126 Likes Received: 0 Trophy Points: 16 Anyone know why this is failing on a centos 6.x X64 box? Annoyingly it reverts back to the previous Apache version even if I've selected the options Not to. -- Begin step 'set php_ini for PECL and PEAR' -- !! '/usr/local/bin/pear config-set php_ini /usr/local/lib/php.ini system' failed with exit code '65280' !! !! Restoring original working apache !! !! Executing '/scripts/initsslhttpd' !! !! Restarting 'httpd' ... !! !! 'httpd' restart complete. !! Building global cache for cpanel...Done !! Executing '/scripts/initfpsuexec' !! !! Executing '/scripts/initsslhttpd' !! !! Executing '/scripts/update_apachectl' !! !! Executing '/scripts/enablefileprotect' !!Click to expand... #1 dragon2611, Mar 6, 2013 cPanelKurtN Well-Known Member Staff Member Joined: Jan 29, 2013 Messages: 95 Likes Received: 1 Trophy Points: 8 cPanel Access Level: Root Administrator As root, what do you get when you execute the following commands? > /usr/local/bin/pear config-se
can track all active APARs for this component. APAR status Closed as documentation error. Error description BPXBATCH Return Code Documentation Updates Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of z/OS UNIX System Services * **************************************************************** * PROBLEM DESCRIPTION: Documentation for BPXBATCH return codes * **************************************************************** * RECOMMENDATION: * **************************************************************** Clarification for BPXBATCH return codes is needed. Problem conclusion Book Title - Unix System Services Command Reference Chapter - Appendix D. Running shell scripts or executable files under MVS environments Section - BPXBATCH Return Codes . A - General rules of setting the return code When running a shell script, your joblog should reflect the failure in the script if you code 'set -o errexit' in the script itself. The command 'set -o errexit' tells the non-interactive shell to execute the ERR trap and then exit. As soon as the script encounters an error, processing of the shell script ends, and you may see a console message like: $HASP165 jobname ENDED AT PLPSC MAXCC=23 In the JOBLOG you may find: IEF142I jobname *OMVSEX - STEP WAS EXECUTED - COND CODE 0023 Without 'set -o errexit' coded in your script, the script is going to keep executing even if it encounters an error, and the last shell command issued in your script is what will be reflected in the joblog. If this last shell command is successful, then you get MAXCC=00. . Return Codes < 128 indicate a failure of the command. You need to look at the application script running to determine what the RC means. The script is either setting the return code explicitly or the last command executed in the script has an exit status equalling the RC. . If the Exit Status >= 128 it means that the process was terminated by a signal. Subtract 128 from the RC to get the signal number. A list of signal numbers and their function is documented in: z/OS UNIX System Services Programming: Assembler Callable Services Reference Appendix G - The relationship of z/OS UNIX signals to callable services Table - z/OS UNIX signals . For example, if the return code is 157, the signal numbe