topic how different RUN and RUN/DETACH in Operating System - OpenVMS

how different RUN and RUN/DETACH

BG Jeong — Mon, 18 Jul 2005 09:50:42 GMT

I'd be pleased if anyone could tell me what this mean...
I have to run a detach process in VAX vms system.
but it ocurred error.

$ RUN SYS$SYSTEM:LOGINOUT.EXE -
/INPUT = OA_ROOT:[SDK.ODBCSAMP.SRC]POP_10MIN_RUN_KKK.COM -
/OUTPUT = OA_ROOT:[SDK.ODBCSAMP.SRC]POP_10MIN_KKK.LOG -
/DETACH -
/PROCESS_NAME = POP_10MIN_KKK -
/PRIORITY = 4 -
/BUFFER_LIMIT = 32672 -
/PRIVILEGES = ALL -
/ENQUE = 50000 -
/WORKING_SET = 10240

$ type POP_10MIN_KKK.LOG
%LIB-E-ACTIMAGE, error activating image DSA1:[SYS1.SYSCOMMON.][SYSLIB]CX$ACCESS_SHR.EXE
-SYSTEM-F-EXQUOTA, process quota exceeded
%TRACE-E-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC

00192260 00192260
001DF273 001DF273
001DAAC8 001DAAC8
TP0TCP_S tp0tcp_conn_req 13260 00000214 0010E5D0
TPI_RFC TCONreq 12439 0000005E 0011211E
SKERNEL Str004 9677 00000213 000FEBC3
FSM s_fsm 9585 0000025F 0008BD27
MGMT s_connect 9696 00000186 0008DA1A
PSEND pxPCONREQ 14600 00000366 0009FE9E
PPDU ppduCP 13202 000004C1 00097405
PKERNEL paCONREQ 13528 000000E0 00092FCC
PMAIN p_fsm 13162 000000C4 00094FC4
PMANAGEM p_connect 13861 00000153 00095B0B
RDAERCV RDA_aeSndPpdu 24090 000000C1 000B9569
ROUTE AL_sacfRoute 13715 000000B2 000EDDD6
FLOWSND AL_sacfCreditSnd 15520 0000012F 0008BA33
FLOWSND AL_sacfUStopSnd 15395 000001D9 0008B839
FLOWSND AL_sacfFlowSnd 15230 0000009F 0008B547
ROUTE AL_sacfRoute 13715 000000B2 000EDDD6
RDAFSND rda_sacfSnd 18893 0000019E 000BBFDE
RDAOSND rda_saoSnd 20459 00000389 000C9BDD
RDAESND rda_aeSnd 21485 0000026E 000B9E16
SURUTIL AL_surSendToAe 13773 00000122 0010BD0E
RDASGSND rda_surSnd 22600 000002B9 000CC8A1
RDACEVNT RDA_cliSendEvent 23372 000000D5 000ACBCD
RDACCONN rda_cliConnect 25224 000004A9 000A8D71
EWOCONN SQLConnect 11823 0000024B 0007FE6F
POP_10MIN_KKK main 4934 000000D2 0006DAD2
connection Error !!!.Retry after 10sec

I tested various way(increasing /Working_set...) to run that process but it's same result.

It is very stange result that it's running ok when just run process below.

$ RUN POP_10MIN_RUN_KKK.COM
connection OK !!!.

Any ideas?

SYSGEN> SHOW WS
Parameter Name Current Default Min. Max. Unit Dynamic
-------------- ------- ------- ------- ------- ---- -------
WSMAX 28700 1024 60 1048576 Pages

$ show mem
............
DISK$OPENVMS062:[SYS1.SYSEXE]SWAPFILE.SYS
34000 34000 34000
DISK$OPENVMS062:[SYS1.SYSEXE]PAGEFILE.SYS
124976 -136557 142408

Does it mean that there is something wrong in SWAPFILE? is that not enough?

Re: how different RUN and RUN/DETACH

Richard W Hunt — Mon, 18 Jul 2005 10:30:56 GMT

Syntax $ RUN program

Runs the program under your account using your current login quotas.

Syntax $ RUN/DETACHED

Runs the program under some account (including yours) using the SYSTEM PQL parameters, quotas, and limits unless you specify the limits with some options that occur in the run command.

I would suggest looking at your SYSGEN PQL parameters and comparing them to your own account's similar quotas. Probably you will find that one of the PQL values is much lower than the corresponding quota in your account.

Re: how different RUN and RUN/DETACH

Eberhard Wacker — Mon, 18 Jul 2005 13:30:24 GMT

Hi,
first trial: put a set verify and afterwards a show proc/quotas at the start of your input procedure a) to see at which point exactly the problem starts and b) to be able to compare the run/detach quotas values with your interactive process ones.

Much more better: if the process is running a while then you have the chance to investigate him more in detail.
There exist a lot of procedures who makes this using the lexical function f$getjpi, one sample:
http://dcl.openvms.org/stories.php?story=03/06/03/0022504

From my experience in many cases it's the pagefile quota along with
-SYSTEM-F-EXQUOTA, process quota exceeded
My proposal: simply double or triple the value of PQL_DPGFLQUOTA and test it.

Cheers,
EW

Re: how different RUN and RUN/DETACH

Eberhard Wacker — Mon, 18 Jul 2005 13:44:16 GMT

Hi again,
put also a $ wait 0:3 or so at the start of your input procedure then you have enough time to look for the PID of the process POP_10MIN_KKK and to investigate it.
Cheers,
EW

Re: how different RUN and RUN/DETACH

John Gillings — Mon, 18 Jul 2005 14:33:12 GMT

BG,

Try this:

$ RUN SYS$SYSTEM:LOGINOUT.EXE -
/INPUT = OA_ROOT:[SDK.ODBCSAMP.SRC]POP_10MIN_RUN_KKK.COM -
/OUTPUT = OA_ROOT:[SDK.ODBCSAMP.SRC]POP_10MIN_KKK.LOG -
/DETACH -
/PROCESS_NAME = POP_10MIN_KKK -
/AUTHORIZE

Adding /AUTHORIZE will copy process quotas and privileges from the UAF. Note that /AUTHORIZE *ONLY* works when running LOGINOUT. It will also OVERRIDE several other qualifiers.

In this case, I'd guess the low quotas to be FILE_LIMIT or PAGE_FILE, BUT this kind of error is dependent on system specific settings of PQL parameters.

Any serious detached process needs a fully populated set of quotas and privileges. You can't depend on SYSGEN PQL_D* and PQL_M* values.

Have a look at procedures in SYS$STARTUP to find RUN commands with all quota qualifiers specified. Cut and paste into your procedure and set ALL quotas to reasonable values.

Re: how different RUN and RUN/DETACH

comarow — Mon, 18 Jul 2005 16:12:48 GMT

a detrached process, as they say get it's quotas from pql_d
while run gets it from UAF.
When the program dies,
anal/system
show sum
and find the process
sho proc/index
and chances are you will set the shortage.

Of course, you could shot gun it, and give the run/detached all the quotas of your interative processes and you are done.

Re: how different RUN and RUN/DETACH

BG Jeong — Mon, 18 Jul 2005 18:05:40 GMT

Thank you for the quick reply to my question.
it's ok that that command run with /Authorize.
Have a nice day.