- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: can't start detached process with sys$system:l...
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
Forums
Discussions
Discussions
Discussions
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
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
01-18-2006 04:42 AM
01-18-2006 04:42 AM
run /detached /augh /input='infile /output='outfile /error='errfile /proc='procname sys$system:loginout.exe
type 'infile
$! starter.com
$ run tempdir:blah.exe
blah.exe contains an infinite-loop that appends a small message to a tempfile every few seconds. I can check the file to see if the process is running.
After the run command, I get a message telling me the id of the new process, but blah.exe never seems to get started, and the new process is either not started, or stops immediately.
If I issue the run command with blah.exe as the file to be executed (instead of loginout) it works, but I am using the input since I will soon need to pass parameters into the app.
I did see messages posted that the detached process would not have access to certain logicals, so I tried absolute addresses in place of logicals, but that made no difference.
Also, just for kicks, i tried running loginout interactively and it ended my session. Didn't know if this was normal or not since I have been unable to find documentation about what loginout actually does (and how).
Thanks in advance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2006 04:44 AM
01-18-2006 04:44 AM
Re: can't start detached process with sys$system:loginout.exe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2006 05:18 AM
01-18-2006 05:18 AM
Re: can't start detached process with sys$system:loginout.exe
I presume that "augh" is only a typo in your posting and not the code.
Does 'outfile' get created? If so, what are its contents?
Use VMS ACCOUNTNG to determine the final status of the job - it will likely provide a clue.
$ ACCO/FULL/ID=xxxxxxxx
where those x's are replaced by the PID that you observe when the detached job is started.
> what loginout actually does
Either performs the requisite actions to accomplish a login or a logout. Since you were already logged it knew to log you out :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2006 06:08 AM
01-18-2006 06:08 AM
Re: can't start detached process with sys$system:loginout.exe
Do you have Accounting turned on? if so have you looked for accounting records for the process start/termination?
Do you get a logfile created for outfile? If you did get an OUTFILE created, there should be some message(s) in it.
All of your apostrophes should be in matched pairs. Your command should be
run /detached /augh /input='infile' /output='outfile' /error='errfile' /proc='procname' sys$system:loginout.exe
The way you typed it in will not evaluate properly. If you actually had the command the way you typed it in here, you probably had some of the symbol interpretation fail which would have made the run fail to open the input or output. You should see that logged in the accounting record(s) for the process.
Robert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2006 06:15 AM
01-18-2006 06:15 AM
Re: can't start detached process with sys$system:loginout.exe
Oh well !!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2006 06:20 AM
01-18-2006 06:20 AM
Re: can't start detached process with sys$system:loginout.exe
In this case the symbols in the command line will translate correctly due to the trailing space delimeter for each of the symbols introduced with a single-quote character. However, I agree that it is bad policy to not pair up the quotes.
As noted, "/augh" is incorrect. But, the fact that command execution resulted in the creation of a process indicates that this wasn't actually part of the command line that was executed as it would have been rejected by DCL and the RUN would never have executed at all.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2006 06:25 AM
01-18-2006 06:25 AM
Re: can't start detached process with sys$system:loginout.exe
I will keep this thread open for a little longer in case it starts acting up again.
Yes, augh was a typo.
Thanks for the suggestions; hopefully this stays "fixed"
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2006 06:26 AM
01-18-2006 06:26 AM
Re: can't start detached process with sys$system:loginout.exe
Thanks for the correction -- I have to say though that it is so easy to make a mistake and leave out the blank and I have been bitten so many times by mismatched apostrophes and/or quotation marks. There have been some bizarre commands executed because of mismatches -- and some cases were very difficult to debug. One reason why I do really like to use DCL_CHECK on procedures that are going to become production code. I don't always agree with everything DCL_CHECK flags, but at least I get flagged on everything of importance.
Another possibility is a security issue -- if the requested output file or input file are not accessible by the user starting the detached process, so it might be helpful to do a REPLY/ENABLE=SECURITY before doing the run command and see if you get any OPCOM alerts.
Robert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2006 02:30 AM
07-24-2006 02:30 AM
Re: can't start detached process with sys$system:loginout.exe
run /detached /input=test.com sys$system:loginout.exe
with test.com:
$ runexe=="data1:[user.mohren_j]test"
$ runexe
$ exit
With acco/full/id=
Thanks in advance for your help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2006 02:38 AM
07-24-2006 02:38 AM
Re: can't start detached process with sys$system:loginout.exe
I also specify /input=f$parse("file") because loginout doesn't understand (all) logicals.
I would still check with accounting why the startup failed.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2006 02:54 AM
07-24-2006 02:54 AM
Re: can't start detached process with sys$system:loginout.exe
For self-educational purposes, add a SHOW LOGICALS to the command file.
As has been noted, what results from a RUN/DETACH is not precisely what gets created by an interactive, network, remote, or batch login. If your program depends (explicitly or implicitly) on a presumption that certain logical names were defined, you may be in for a problem.
Also check the values of LNM$FILE_DEV in the Process Directory (Logical Name table LNM$PROCESS_DIRECTORY).
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2006 02:55 AM
07-24-2006 02:55 AM
SolutionIn your case, you DO get the logicals. It's when you specify /uic that you don't get them. /auth + /detach cause a full login to be done.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2006 03:04 AM
07-24-2006 03:04 AM
Re: can't start detached process with sys$system:loginout.exe
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2006 03:06 AM
07-24-2006 03:06 AM
Re: can't start detached process with sys$system:loginout.exe
The full login may be done, but a large caution remains appropriate.
Many (and I mean MANY) LOGIN.COM procedures incorrectly presume that INTERACTIVE, NETWORK, and BATCH are the only responses. They have been designed or tested with the Detached Process case, which will yield OTHER.
It should not be a problem, but caution and vigilence is still recommended.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2006 03:06 AM
07-24-2006 03:06 AM
Re: can't start detached process with sys$system:loginout.exe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2006 03:11 AM
07-24-2006 03:11 AM
Re: can't start detached process with sys$system:loginout.exe
I worked on looking for the problem, and I meanwhile got something in my outfile:
Error opening primary input file sys$input
Error in device name or inappropriate device type for operation
But I don't see where sys$input is used!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2006 03:17 AM
07-24-2006 03:17 AM
Re: can't start detached process with sys$system:loginout.exe
show logical * (first line)
in my input file. But not even the logicals appear in my output
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2006 03:21 AM
07-24-2006 03:21 AM
Re: can't start detached process with sys$system:loginout.exe
As a point of ITRC Forum etiquette, a new thread should really be opened.
However, as Wlm mentioned earlier, check the accounting logs. If the first line of the command file does not execute, then the LOGIN.COM (if you are specifyig /AUTHORIZE) or something else is not right.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2006 03:25 AM
07-24-2006 03:25 AM
Re: can't start detached process with sys$system:loginout.exe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2006 03:38 AM
07-24-2006 03:38 AM
Re: can't start detached process with sys$system:loginout.exe
/input='f$parse("file")'
Idem for /output and /error.
Wim
(didn't see that it was an old one. Time flies by very fast)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2006 03:56 AM
07-24-2006 03:56 AM