- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Odd error logged to OPCOM from SCP.
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2010 04:42 PM
тАО02-04-2010 04:42 PM
In Basic:
scp_cmd = 'scp "-Q" TEST.F "brady:test.f"'
sts = lib$spawn( &
scp_cmd !command! &
, !input-file! &
, !output-file! &
, !flags! &
, !process-name! &
, !process-id! &
,loc( exit_sts ) !completion-status-address! &
, !byte-integer-event-flag-num! &
, !AST-address! &
, !varying-AST-argument! &
)
Neither sts nor exit_sts have errors after the call.
The file is successfully copied.
I'm getting the following logged:
%%%%%%%%%%% OPCOM 4-FEB-2010 18:54:38.78 %%%%%%%%%%%
Message from user JON on JOONYA
OpenVMS$initialize_unix_env error, status: : error 00000002
,Cannot chdir to SYSтЧЖ
(The 0000000002 may be C/Unix EACCES?)
The text string "initialize_unix_env" appears in a bunch of TCPIP SSH .exe files.
The error is only reported if the spawning program is run/detached.
When the program that executes the spawn is run interactively or in a batch
no error is logged.
$ run sys$system:loginout -
/process_name='process_name' -
/detached -
/input='input' -
/output='logfile' -
/nodebug -
/error='errfile'
(quota switches omitted)
The input file is the same for a submit or run/detached:
$ run run:SCP_HP_TEST
The problem occurs on both an Alpha and an Itanium.
$ scp "-V"
tcpip$ssh_scp2.exe: SSH Secure Shell OpenVMS (V5.5) 3.2.0 on AlphaServer ES45
Model 3B - VMS V8.3
$ scp "-V"
tcpip$ssh_scp2.exe: SSH Secure Shell OpenVMS (V5.5) 3.2.0 on HP rx2620
(1.60GHz/3.0MB) - VMS V8.3
Any ideas?
Jonathan
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2010 07:04 PM
тАО02-04-2010 07:04 PM
Re: Odd error logged to OPCOM from SCP.
Detached processes are very different from interactive or batch. My guess is the most likely cause is lack of some or other quota. Your RUN command doesn't specify any quotas, and will therefore get the SYSGEN PQL_D* values, possibly boosted to PQL_M* values. Typically these are just sufficient to get a process running, but rarely enough to do anything useful.
My general rule is, any detached process started without a fully populated PQL is an EXQUOTA looking for a place to happen.
Look for a RUN/DETACHED command anywhere in SYS$STARTUP, copy the qualifier list and populate it with reasonable values. You can use RUN/AUTHORIZE as a shortcut to use the quotas from your UAF record, but be aware that it may override other qualifiers (like /PROCESS_NAME)
If quotas don't help, I'd be looking for some other environmental change, possibly something defined in LOGIN or SYLOGIN (which aren't run for detached processes). Try adding:
$ @SYS$MANAGER:SYLOGIN
$ @SYS$LOGIN:LOGIN
to your input procedure?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2010 09:11 PM
тАО02-04-2010 09:11 PM
Re: Odd error logged to OPCOM from SCP.
Sorry, I just noticed you said quota qualifiers were omitted. Nevertheless, please make sure they're all present and all adequate.
What does the rest of the fragment "Cannot chdir to SYS" say?
Try replacing your SPAWN command with SHOW LOGICAL and SHOW SYMBOL in interactive and detached modes. See if there are any significant differences.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2010 11:30 PM
тАО02-04-2010 11:30 PM
Re: Odd error logged to OPCOM from SCP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2010 11:54 PM
тАО02-04-2010 11:54 PM
Solutioneven if running loginout, if the /AUTHORIZE is missing from run/detach, then the following logicals are not defined:
$ show logical sys$login
%SHOW-S-NOTRAN, no translation for logical name SYS$LOGIN
$ show logical sys$login_device
%SHOW-S-NOTRAN, no translation for logical name SYS$LOGIN_DEVICE
$ show logical sys$scratch
%SHOW-S-NOTRAN, no translation for logical name SYS$SCRATCH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-05-2010 06:16 AM
тАО02-05-2010 06:16 AM
Re: Odd error logged to OPCOM from SCP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-05-2010 06:58 AM
тАО02-05-2010 06:58 AM
Re: Odd error logged to OPCOM from SCP.
I notice that the command file on production that runs the detached job was written in 1987 for a VAX 8650, and the quotas switches that gave the job extra resources back then, now cut it way back from the account defaults :). Of course the customer hasn't upgraded to the next version which has only been out since 1993...:(.
Anyway thanks to all, and particularly Joseph
Jonathan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-05-2010 07:38 AM
тАО02-05-2010 07:38 AM
Re: Odd error logged to OPCOM from SCP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-05-2010 08:17 AM
тАО02-05-2010 08:17 AM
Re: Odd error logged to OPCOM from SCP.
>>>
Joseph Huber takes the prize
<<<
... but he did not get it yet!!
Only YOU ( "Question Author" ) can do that:
reopen the thread
in each answer's title bar pull down the Points Menu
vauate each answer
and finally hit "Submit Points".
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-05-2010 09:51 AM
тАО02-05-2010 09:51 AM
Re: Odd error logged to OPCOM from SCP.
other hand my partial points given to others did not show up. I tried reopening and setting them again got the same result.
Jonathan