Software development, photography, jokes, ....


Sites by me

tas-logoTransportation Administration System
snoezelkussen-logo-kleinstSnoezelen Pillows for Dementia
ikzoekeenbegeleider-logoBegeleiders voor gehandicapten
Laat uw hond het jaarlijkse vuurwerk overwinnen
Betuweroute en Kunst
logo 50x50Hey Vos! Je eigen emailadres?
Kunst in huis? Nicole Karrèr maakt echt bijzonder mooie dingen
nettylogo2Kunst in huis? Netty Franssen maakt ook bijzonder mooie dingen

Hosting Favorites

ANU Internet Services
XEL Media


Google Translate
jQuery UI
YourHead Stacks API
Favicon Generator.
Password Generator.
Check HTTPS problems

Marc's Place


Displays a message at a system operator's terminal and optionally requests a reply. All messages are logged at the operator's console and in the operator's log file, if that file is initialized. To use this command, you must start the operator communication process (OPCOM) at boot time by specifying the DCL command @SYS$SYSTEM:STARTUP OPCOM in the site-specific startup command file, SYS$MANAGER:SYSTARTUP.COM. Format REQUEST message-text 2 Parameter message-text Specifies the text of the message to be displayed. The string can be up to 128 characters. If the string contains spaces, special characters, or lowercase characters, enclose it in quotation marks (" "). 2 Qualifiers /REPLY Requests a reply to the message and issues a unique identification number to which the operator sends the response. The system displays a message that the operator has been notified; you cannot enter any commands until the operator responds. If you press Ctrl/C before the operator responds, you can then enter another message to the operator, or press Ctrl/Z to cancel the request. /TO /TO=(operator[,...]) Specifies one or more operators to whom you want to send the message. Possible keywords are as follows: CARDS Sends the message to operators designated to respond to card reader requests. CENTRAL Sends the message to the central system operator. CLUSTER Sends the message to operators designated to respond to cluster-related requests. DEVICES Sends the message to operators who mount and dismount disks. DISKS Sends the message to operators who mount and dismount disk volumes. NETWORK Sends the message to the network operator. OPER1 to OPER12 Sends the message to operators identified as OPER1 to OPER12. PRINTER Sends the message to operators designated to handle print requests. SECURITY Sends the message to operators designated to respond to security-related requests. TAPES Sends the message to operators designated to mount and dismount tape volumes. 2 Examples 1.$ PRINT/COPIES=2/QUEUE=LQ_PRINT REPORT.OUT/FORM=LETTER Job REPRT (queue LQA1, entry 401) pending $ REQUEST/REPLY/TO=PRINTER - _$"Have queued job 401 as FORM=LETTER; can you print it?" %OPCOM-S-OPRNOTIF, operator notified, waiting...10:42:16.10 %OPCOM-S-OPREPLY, AFTER 11:00 14-DEC-1994 10:25:32.40, request 3 completed by operator OPA0 In this example the PRINT command requests that multiple copies of a file be printed using a special paper (/FORM=LETTER). After queueing the job to the printer, the REQUEST command sends a message to the system operator. The operator sends a reply after completing the request. 2.$ REQUEST/REPLY "Are you there?" %OPCOM-S-OPRNOTIF, operator notified, waiting...14:54:30.33 <Ctrl/C> REQUEST-Enter message or cancel request with ^Z REQUEST-Message?<Ctrl/Z> %OPCOM-S-OPRNOTIF, operator notified, waiting... 14:59:01.38 %OPCOM-F-RQSTCAN, request was canceled In this example the REQUEST command issues a message and requests a response. When no operator replies to the question, Ctrl/C is used to interrupt the request; then Ctrl/Z is used to cancel it.

© 1997- Marc Vos (and others)   -   Privacy Statement   -    Contact Me

On this website, Google Analytics is used to track visitor statistics. These are anonymised data about the number of visitors, which pages they visit on this site, from which regions they visit, which web browsers they use, etc.. You will also see non-personalised ads via Google AdSense. Cookies from Paddle or Paypal are placed when you click on a 'Buy now!' or 'Donate!' button, and possible cookies from Disqus when you use that system to comment on one or more blogposts.
Privacy Statement