Document revision date: 30 March 2001

## OpenVMS DCL Dictionary

Previous | Contents | Index

## SET DISPLAY

> Directs the output of an OpenVMS DECwindows application. Output can be directed from any processor running a DECwindows application, including workstations, to any DECwindows workstation.

> Both source and destination nodes must be part of the same network.

### Format

> SET DISPLAY [display-device]

### Parameters

> #### display-device

> Specifies a logical name for the workstation display you are creating or modifying. If you are directing application output to multiple workstation displays, you can use different logical names to point to each display. If you do not specify a display-device parameter, the logical name DECW$DISPLAY is used. This means that, by default, application output will be displayed on the workstation display device referred to by DECW$DISPLAY.

> By entering the command SHOW DISPLAY, you can see the default workstation node where applications will be displayed, as well as related device, screen, and transport information.

> If you specified your own logical name in the SET DISPLAY/CREATE command, include that logical name in the SHOW DISPLAY command.

### Description

> DECwindows gives you the ability to run applications across a network. The SET DISPLAY command gives you the ability to perform the following tasks:
> - Direct the output from applications running on your workstation to another workstation.
> - Direct the output from applications running on remote processors to your workstation. Although the application runs on another processor, it looks the same as any other application running locally on your workstation.

> By running applications on a remote processor for local display on your workstation monitor, you can take advantage of larger computers that might be better suited to a specific computing task. By default, applications running on your workstation are displayed on your workstation. While DECwindows must be available on both nodes, only the display node must be a workstation.

> The SET DISPLAY command affects only those applications running from the process from which you enter the command. This means that although you might be running one application on your workstation and displaying it on another workstation, you can continue to run applications on your workstation for display in other windows on your workstation as illustrated in Figure DCLII-1.

> Figure DCLII-1 Running Remote and Local Applications

To direct application output to another DECwindows workstation, enter the SET DISPLAY command in the following form:

`SET DISPLAY/CREATE/NODE=workstation_display/TRANSPORT=transport_name`

If you do not specify the /TRANSPORT qualifier, the value defined by the logical DECW$SETDISPLAY_DEFAULT_TRANSPORT is used. If this logical is not defined, the value of DECNET is used as the default.

Subsequently, you can redirect the display to other workstation devices by entering a DCL command in the following form:

`SET DISPLAY/NODE=workstation_display`

By default, you are authorized to run applications locally on your workstation. You cannot log in to another node and direct applications to display on your workstation unless you explicitly authorize yourself to do so. This prevents unauthorized users on other nodes in the network from directing output to or receiving input from your workstation without your specific permission.

Make sure the node name you use in the SET DISPLAY command matches the node name from which you are authorized to display applications. For example, if you specify SET DISPLAY/CREATE/NODE=HUBBUB from your node ZEPHYR, and are not authorized to display applications on the DECwindows workstation HUBBUB, DECwindows reports that you are not authorized to use that display. For information about displaying applications on other workstation nodes and using the DECwindows Session Manager to authorize remote connections, refer to the DECwindows documentation.

By using one of the following qualifiers: /EXECUTIVE_MODE, /SUPERVISOR_MODE, or /USER_MODE, you can specify the mode of the device you are creating. The default is the /SUPERVISOR_MODE qualifier.

See also the description of the SHOW DISPLAY command for more information.

### Qualifiers

> #### /CREATE

> Creates the workstation display device (WSAn:) on which a DECwindows application is displayed. You must specify the /CREATE qualifier the first time you use the SET DISPLAY command, but you need not respecify it if you continue to redirect output from applications to other workstations with subsequent SET DISPLAY commands.

> When you specify the /CREATE qualifier without the /NODE qualifier, the workstation device defaults to the current node. Additionally, if you omit the /TRANSPORT qualifier, the transport defaults to either the value specified by the DECW$SETDISPLAY_DEFAULT_TRANSPORT logical, if defined, or to DECNET.

> #### /DELETE

> Cancels the redirected display by deassigning the logical name DECW$DISPLAY and deleting the created display device. If you specified a logical name as the display-device parameter with the SET DISPLAY/CREATE command, entering the SET DISPLAY/DELETE display-device command cancels the redirected display by deassigning the logical name you specified and deleting the created display device.

> The DECwindows Session Manager defines DECW$DISPLAY in your job logical name table when you open a terminal (DECterm) window. When you redirect application output to another workstation with the SET DISPLAY/CREATE command, an additional DECW$DISPLAY logical name is defined in your process logical name table. This definition supersedes the definition in the job logical name table. Output from applications run from the process in which you executed the SET DISPLAY/CREATE command will be displayed on the workstation referred to by the definition of DECW$DISPLAY in the process logical name table. Enter the SHOW DISPLAY command to see where this application will be displayed. To see whether multiple definitions for DECW$DISPLAY exist, enter the command SHOW LOGICAL DECW$DISPLAY.

> If DECW$DISPLAY is still defined (for example, in the job logical name table) after you specify the /DELETE qualifier, any DECwindows applications run from this process will be displayed on the workstation device to which output is now directed. Enter the SHOW DISPLAY command if you are unsure of the node to which DECW$DISPLAY refers.

> Caution If you modify or delete the definition of DECW$DISPLAY from the job logical name table, you will be unable to start another session. Be careful not to specify the /DELETE qualifier without having first redirected the display with the SET DISPLAY/CREATE command.

> You cannot specify the /DELETE and /CREATE qualifiers on the same command line.

> #### /EXECUTIVE_MODE

> Creates an executive-mode device and assigns the logical name DECW$DISPLAY to point to it. This qualifier must be used with the /CREATE qualifier. Devices created with the /EXECUTIVE_MODE qualifier are deleted only in the following situations:
> - They are explicitly deleted with the /DELETE qualifier.
> - The system is rebooted.

> To modify or delete executive-mode devices, you must have SYSNAM (system logical name) privilege.

> #### /NODE=workstation_display

> Defines the workstation on which you want to display DECwindows applications. The node name you provide cannot be a cluster alias (a name that represents multiple nodes configured in an OpenVMS Cluster), but must instead identify an actual node.

> You must create a workstation display device with the /CREATE qualifier before you can redirect the output from applications to other workstations. Do not enter the SET DISPLAY/NODE=workstation_display command without having previously specified the /CREATE qualifier.

> When you specify the /CREATE qualifier without the /NODE qualifier, the workstation defaults to the current node.

> Make sure that you are authorized to display applications on the workstation you specify. For more information about using the DECwindows Session Manager to authorize yourself to display applications from other nodes, refer to the DECwindows documentation.

> Each node, both source and destination, must be defined in the other's network node database. For example, to display applications on node HUBBUB from ZEPHYR, HUBBUB must be entered in ZEPHYR's network node database, and ZEPHYR must be entered in HUBBUB's network node database. In addition, users on ZEPHYR must be authorized in the DECwindows Session Manager to display applications on HUBBUB. For information about entering nodes in a network node database, refer to the DECnet for OpenVMS Networking Manual and the DECnet for OpenVMS Network Management Utilities manual. These manuals are available on the Documentation CD-ROM.

> #### /SCREEN=screen-number

> Defines the screen to be associated with this display device. In some hardware configurations, the system supports more than one screen. In such a configuration, you can specify the screen to which the application is directed.

> #### /SERVER=server-number

> Defines the server to be associated with the display device indicated by the display-device parameter to the SET DEVICE command. Using the transport mechanism, the server passes data between the user and the application. In some hardware configurations, the system supports more than one server. In such a configuration, you can specify the server to which the application is directed. If you do not specify the display-device parameter, the SET DISPLAY/SERVER command associates the server with the display device indicated by the logical name DECW$DISPLAY.

> #### /SUPERVISOR_MODE (default)

> Creates a supervisor-mode device and assigns the logical name DECW$DISPLAY to point to it. This qualifier must be used with the /CREATE qualifier. When the user logs out, the device is deleted.

> #### /TRANSPORT=transport-name

> Defines the mechanism, for example, DECnet or local, that passes information between the application and the workstation. The transport mechanism is used to send input from the user to the application and output from the application to the display device. The transport-name can be one of the following values:
> - TCPIP or DECNET
>   Specifies the appropriate network transport for applications running and displaying on different nodes. You can specify the default transport value used with the SET DISPLAY/CREATE command by defining the DECW$SETDISPLAY_DEFAULT_TRANSPORT logical in either the job, process, or system table. The value of this logical is then used each time you enter the SET DISPLAY/CREATE command without the /TRANSPORT qualifier. If you specify neither the qualifier nor the logical, the value of DECNET is used as default.
> - LOCAL
>   Optimizes the performance of applications running and displaying on the same node.

> #### /USER_MODE

> Creates a user-mode display device and assigns the logical name DECW$DISPLAY to point to it. This qualifier must be used with the /CREATE qualifier. The lifetime of a user-mode device is one DECwindows image: when the next DECwindows image exits, the device is deleted.

###

#### Examples

#1
    $ SHOW DISPLAY
      Device:     WSA1: [super]
      Node:       0
      Transport:  LOCAL
      Server:     0
      Screen:     0

    $ SET DISPLAY/CREATE/NODE=ZEPHYR/EXECUTIVE_MODE
    $ SHOW DISPLAY
      Device:     WSA2:  [exec]
      Node:       ZEPHYR
      Transport:  DECNET
      Server:     0
      Screen:     0
    $ SPAWN/NOWAIT/INPUT=NL: RUN SYS$SYSTEM:DECW$CLOCK

    $ SET DISPLAY/DELETE

    $ SHOW DISPLAY
      Device:     WSA1:  [super]
      Node:       0
      Transport:  LOCAL
      Server:     0
      Screen:     0

> In this example, you are logged in to your workstation (device WSA1:), here referred to as node 0. (0 is the standard shorthand notation for representing your node.) You want to run the DECwindows Clock on your workstation and display it on another workstation, ZEPHYR.

> Assuming you are authorized to display applications on ZEPHYR, you redirect the application's output to ZEPHYR with the SET DISPLAY command. The device created on ZEPHYR is an executive-mode device. You enter the SHOW DISPLAY command to verify the location of the redirected display. You then run Clock. When you finish running Clock, you disable the redirected display by entering the SET DISPLAY/DELETE command. Finally, you enter the SHOW DISPLAY command to verify that any applications subsequently run on your node will also be displayed there.

> Note that a new workstation display device, WSA2, is created when you enter the SET DISPLAY/CREATE command. When you cancel the redirected display with the SET DISPLAY/DELETE command, application output is once again displayed on the workstation display device referred to by WSA1.

#2
    $ SET DISPLAY/CREATE/NODE=FLOPSY RABBIT
    $ SHOW DISPLAY RABBIT

     Device:    WSA2:  [super]
     Node:      FLOPSY
     Transport: DECNET
     Server:    0
     Screen:    0

    $ RUN/DETACHED/OUTPUT=WSA2: SYS$SYSTEM:DECW$CLOCK

    $ SET DISPLAY/CREATE/NODE=ZEPHYR ZNODE
    $ SHOW DISPLAY ZNODE

     Device:    WSA3:  [super]
     Node:      ZEPHYR
     Transport: DECNET
     Server:    0
     Screen:    0

    $ RUN/DETACHED/OUTPUT=WSA3: SYS$SYSTEM:DECW$CALENDAR

    $ RUN SYS$SYSTEM:DECW$BOOKREADER
    $ SHOW DISPLAY

     Device:    WSA1:  [super]
     Node:      0
     Transport: LOCAL
     Server:    0
     Screen:    0

> In this example, you are logged in to your node (device WSA1:), and want to direct the output from applications to several workstation displays in the same session. By specifying different logical names in the SET DISPLAY command, you can redirect the output without changing the logical name definition for DECW$DISPLAY. This allows you to display the output from most applications on your default display but occasionally display output on another workstation. You can also continue to run and display applications on your node. In this example, Clock is displayed on node FLOPSY, Calendar is displayed on node ZEPHYR, and Bookreader is displayed on your workstation.

> Note that to run your applications with the DCL command RUN/DETACHED, you must use the device name that equates to the logical display device name you specified in the SET DISPLAY command. Use the SHOW DISPLAY command to obtain this device name.

## SET ENTRY

> Changes the current status or attributes of a job not currently executing in a queue.

> Requires delete (D) access to the job or manage (M) access to the queue.

### Format

> SET ENTRY entry-number[,...]

### Parameter

> #### entry-number[,...]

> Specifies the entry number of the job you want to change. If you specify more than one entry, separate the entry numbers with commas (,).

> The system assigns a unique entry number to each queued print or batch job in the system. By default, the PRINT and SUBMIT commands display the entry number when they successfully queue a job for processing. These commands also create or update the local symbol $ENTRY to reflect the entry number of the most recently queued job. To find a job's entry number, enter the SHOW ENTRY or the SHOW QUEUE command.

### Description

> The SET ENTRY command allows you to change the status or attributes of one or more jobs, as long as the jobs are not executing currently. You cannot affect individual files within a multifile job with the SET ENTRY command.

> The qualifiers enable you to specify different attributes or delete attributes. Some qualifiers apply to both batch and print jobs. Others are restricted to either batch jobs or print jobs. The defaults for all the SET ENTRY qualifiers are the attributes and status that the job has before you enter the SET ENTRY command.

> This command requires delete (D) access to the job, manage (M) access to the queue, or OPER (operator) privilege.

### Qualifiers

> #### /AFTER=time

> #### /NOAFTER

> Requests that the specified job be held until after a specific time. If the specified time has already passed, the job is scheduled for processing.

> You can specify either absolute time or a combination of absolute and delta times. For complete information on specifying time values, refer to the OpenVMS User's Manual or the online help topic DCL_Tips (subtopic Date_Time).

> Note Releasing or rescheduling a job before its submission time is not supported for security reasons. Therefore, if you set the system time to a future time and submit a job on a node where the queue manager is running, you cannot release or reschedule that job back to the present time if you reset the system time. For example, you can set the system time to a future time of January 1, 2020 and submit a job to run on January 9, 2020; however, if you set the system time back to the present time and try to release the job to the present time, the job will be released to January 1, 2020. This situation impacts the following qualifiers: /AFTER, /NOHOLD, and /RELEASE.

> To specify /AFTER for a job on hold, you must also specify /NOHOLD in order to cause the job to be held only until the specified time. Jobs can be released before the specified time by using the /NOAFTER or /RELEASE qualifier with the SET ENTRY command.

> #### /BURST

> #### /NOBURST

> Controls whether two file flag pages with a burst bar between them are printed preceding each file in a job.

> Use the /[NO]BURST qualifier to override the /DEFAULT qualifier options that have been set for the output queue you are using. The /[NO]BURST qualifier does not override the /SEPARATE qualifier options set for the queue.

> When you specify the /BURST qualifier for a file, the /[NO]FLAG qualifier does not add or subtract a flag page from the two flag pages that are printed preceding a file.

> #### /CHARACTERISTICS=(characteristic[,...])

> #### /NOCHARACTERISTICS

> Specifies the name or number of one or more characteristics to be associated with the job. Characteristics can refer to such things as color of ink. If you specify only one characteristic, you can omit the parentheses.

> A characteristic's number must range from 0 to 127. To see which characteristics have been defined for your system, use the SHOW QUEUE/CHARACTERISTICS command. To see which characteristics are associated with a particular queue, use the SHOW QUEUE/FULL command.

> A print job can be processed on an execution queue if none, some, or all of the characteristics associated with the queue also are associated with the job. That is, the job's characteristics must be a subset of the queue's characteristics. However, if any of the characteristics associated with the job are not associated with the queue, the job remains pending until one or more of the following occurs:

> - The characteristics specified with the queue are changed to make the job's characteristics a subset of the queue's characteristics (using, for example, the SET QUEUE/CHARACTERISTICS command).
> - The characteristics specified with the job are changed to make the job's characteristics a subset of the queue's characteristics (using, for example, the SET ENTRY/CHARACTERISTICS command).
> - The job is moved to a queue on which all the job's characteristics have been specified (using, for example, the SET ENTRY/REQUEUE command).
> - The job is deleted (using, for example, the DELETE/ENTRY command).

> #### /CLI=filename

> Specifies the name of a command language interpreter (CLI) to use in processing the batch job. The file name specifies that the CLI be SYS$SYSTEM:filename.EXE. If you do not specify the /CLI qualifier, the job is run by the CLI specified in the user authorization file (UAF), or whatever CLI was specified when the job was originally submitted to the queue.

> #### /COPIES=n

> Specifies the number of copies to print. The value of n can be any number from 1 to 255. When you use the /COPIES qualifier with the SET ENTRY command, the number of copies can apply only to the entire print job. You cannot use this qualifier to specify different numbers of copies for individual files within a multifile job.

> #### /CPUTIME=time

> Specifies a CPU time limit for the batch job. You can specify the time parameter as delta time, the value 0, INFINITE, or NONE. If the queue on which the job executes has a defined CPUMAXIMUM value, the smaller of the specified job and queue values is used. If the queue on which the job executes does not have a specified maximum CPU time limit, the smaller of the SUBMIT command and user authorization file (UAF) values is used. If the queue on which the job executes does not have a specified maximum CPU time limit and the UAF has a specified CPU time limit of NONE, either the value 0 or the keyword INFINITE allows unlimited CPU time. If you specify NONE, the specified queue or UAF value is used. CPU time values must be greater than or equal to the number specified by the system parameter PQL_MCPULM.

> For more information on specifying CPU time limits, see the CPU Time Limit Specifications and Actions table for the INITIALIZE/QUEUE command. For information on specifying time values, refer to the OpenVMS User's Manual or the online help topic DCL_Tips (subtopic Date_Time).

> #### /FEED

> #### /NOFEED

> Controls whether form feeds are inserted into the print job when the printer reaches the bottom margin of the form in use. You can suppress this automatic form feed (without affecting any of the other carriage control functions that are in place) by using the /NOFEED qualifier.

> When you use the /FEED qualifier with the SET ENTRY command, the qualifier applies to all files in the print job. You cannot use this qualifier to specify form feeds for individual files within a multifile job.

> #### /FLAG

> #### /NOFLAG

> Controls whether a flag page is printed preceding each file in a print job. The flag page contains the name of the user submitting the job, the job entry number, and other information about the file being printed.

> Use the /[NO]FLAG qualifier to override the installation-defined defaults that have been set for the output queue you are using or to override the qualifier specified in the PRINT command that queued the job.

> #### /FORM=form

> Specifies the name or number of the form to be associated with the print job. If you omit the /FORM qualifier, the default form for the execution queue is associated with the job.

> Forms have attributes such as print image width and length or paper stock, which the print symbiont associates with a job when the job is processed. To see which forms have been defined for your system, use the SHOW QUEUE/FORM command. To find out which form is mounted currently on a particular queue and which form is specified as that queue's default form, use the SHOW QUEUE/FULL command.

> The stock of the form associated with the job must match the stock of the form mounted on the execution queue on which you want the job to be processed. If the stocks do not match, the job remains pending until one or more of the following occurs:

> - A form with the same stock as the job's form is mounted on the queue (using, for example, the SET QUEUE/FORM_MOUNTED command).
> - A form with the same stock as the queue's mounted form is specified with the job (using, for example, the SET ENTRY/FORM command).
> - The job is moved to a queue on which the stock of the mounted form matches the stock of the job's form (using, for example, the SET ENTRY/REQUEUE command).
> - The job is deleted (using, for example, the DELETE/ENTRY command).

> #### /HEADER

> #### /NOHEADER

> Controls whether a heading line is printed at the top of each output page in a print job.

> #### /HOLD

> #### /NOHOLD

> Controls whether the job is to be made available for processing or held for processing later. If you specify the /HOLD qualifier, the job is not released for processing until you enter SET ENTRY/NOHOLD or SET ENTRY/RELEASE.

> You can use the /NOHOLD qualifier to release jobs that have been held for the following reasons:

> - A job was submitted with the /HOLD qualifier.
> - A completed job is being retained in a queue.
> - A user-written symbiont has refused a job.

> Note Releasing or rescheduling a job before its submission time is not supported for security reasons. Therefore, if you set the system time to a future time and submit a job on a node where the queue manager is running, you cannot release or reschedule that job back to the present time if you reset the system time. For example, you can set the system time to a future time of January 1, 2020 and submit a job to run on January 9, 2020; however, if you set the system time back to the present time and try to release the job to the present time, the job will be released to January 1, 2020. This situation impacts the following qualifiers: /AFTER, /NOHOLD, and /RELEASE.

> #### /JOB_COUNT=n

> Requests that an entire print job be printed n times, where n is a decimal integer from 1 to 255. This qualifier overrides the /JOB_COUNT qualifier with the PRINT command.

> #### /KEEP

> #### /NOKEEP

> Controls whether the batch job log file is deleted after it is printed.

> #### /LOG_FILE[=filespec]

> #### /NOLOG_FILE

> Creates a log file with the specified file specification. You can specify a different device name, as long as the process executing the batch job has access to the device on which the log file will reside. Logical names in the file specification are translated in the context of the process that executes the SET ENTRY command.

> If you omit the /LOG_FILE qualifier and specify the /NAME qualifier, the log file is written to a file having the same file name as that specified by the /NAME qualifier; the file type is .LOG. When you omit the /LOG_FILE qualifier, the job-name value used with the /NAME qualifier must be a valid file name.

> #### /LOWERCASE

> #### /NOLOWERCASE

> Indicates whether the print job must be printed on a printer that can print both uppercase and lowercase letters. The /NOLOWERCASE qualifier means that files can be printed on printers that print only uppercase letters. If all available printers can print both uppercase and lowercase letters, you do not need to specify the /LOWERCASE qualifier.

> #### /NAME=job-name

> Names the job. The job name must be 1 to 39 alphanumeric characters. The SHOW ENTRY and SHOW QUEUE commands display the job name. For batch jobs, the job name is also used for the batch job log file. For print jobs, the job name is also used on the flag page of the printed output.

> The default job name is the name of the first file in the job.

> #### /NOCHECKPOINT

> For a batch job, erases the value established by the most recently executed SET RESTART_VALUE command. For a print job, clears the stored checkpoint so that the job will restart from the beginning.

> #### /NODELETE

> Cancels file deletion for a job that was submitted with the /DELETE qualifier. If you did not specify the /DELETE qualifier when the job was originally submitted to the queue, you cannot use the SET ENTRY command to establish file deletion at a later time. You cannot use the /NODELETE qualifier to cancel deletion of individual files in a multifile job.

> #### /NOTE=string

> Specifies a message of up to 255 characters to appear on the flag page of the print job. Enclose messages containing lowercase letters, blanks, or other nonalphanumeric characters (including spaces) in quotation marks (" ").

> #### /NOTIFY

> #### /NONOTIFY

> Controls whether a message notifies you when your job has been completed or aborted. Notification is sent to any terminal session on the same OpenVMS Cluster system to which you are logged in.

> #### /OPERATOR=string

> Specifies a message string of up to 255 characters to be sent to the operator just before the print job begins to print. Enclose the message in quotation marks (" ") if it contains spaces, special characters, or lowercase characters.

> #### /PAGES=([lowlim,]uplim)

> Specifies the number of pages to print for the specified job. You can use the /PAGES qualifier to print portions of long files. By default, all pages of the file are printed. When you use the /PAGES qualifier with the SET ENTRY command, the qualifier can apply only to an entire job. You cannot use this qualifier to specify different numbers of pages to be printed for individual files within a multifile job.

> Previous | Next | Contents | Index

> | privacy and legal statement |
> 9996PRO_052.HTML