Bits of (virtually unrelated) information
ACCVIO
This error is one of the most severe errors you can run into, but it never is a system-fatal one: it is the reult of a programming error - without exception.
Read about it in the AccVio page.
TCPIP-E-LPD_REQREJECT
You may encounter the error if you're printing to a queue that uses the LPD-symbiont, and that passes the data either directly to the printer, or to a print server that will address the physical device. It looks like:
%TCPIP-E-LPD_REQREJECT, print request rejected by !AS (queue !AS)
where the first "!AS" should hold the user name of the request, and the second the queue on which it happened. Sometimes it won't, for instance if your printer is served by a Windows-based printserver, as I found out. Restarting the queue, or the server, will not make a difference. Telnetting to the server, or the printer directly, on port 515 (the default LPD port) will not reject the connection, but happly accept incoming requests. VMS will requeue the job, until a certain number of attempts have failed. If the queue is defined /RETAIN=ERROR the job is kept in the queue - but retained. Accounting just tells the job is cancelled before execution and will be requeued.
The Wizard does give the answer. it's a device problem. Or, in case of a remote server, the LPD server to handle the request.
The solution, in case of a remote server, is simply restart the printers on that machine :). To output the retained entries once more, just do a $ SET ENTRY/RELEASE <entry-list>.
LIB$FIND_FILE
This system service allows you to scan a directory for specific files, but there are some things to think about, as is explained in this document
Run a process under another UIC
There are situations where an image should be run under a different user. There are different solutions to do it - and some are available on the freeware CD's: HLOGIN, JUMP and ASSUME are examples. But sometimes you need full control over such a process, for instance if an environment is very strict. The right way to do this is to create Persona, switch between them and delete them afterwards. The old method: creating a process under another UIC (in DCL: RUN/UIC=, and in a program, the $CREPRC system service where UIC is specified) and executing SYS$SYSTEM:LOGINOUT.EXE to execute a commandprocedure, is highly deprecated. But it's simple and works - mostly. However, keep in mind that the system autorization file is not accessed for quota and therefore, the process will be used with default quota that usually are quite small, and that the login sequence is NOT executed. So you'll need to spefify workingset and other process quota, and you'll have to set up all working context for the process.