| Previous | \Contents | ^Index |
9 If you've installed the DECwindows examples, you'll find D DECW$CDPLAYER.C, .DAT, .EXE, .UIL, and .UID. Copy the .UID and .DAT H files to DECW$USER_DEFAULTS: (typically SYS$LOGIN:), define the logical D name DECW$CD_PLAYER to be the device name of your CD-ROM drive (eg. D DKA400:), give yourself PHY_IO and DIAGNOSE privileges, and run the F .EXE. (These privileges are required, as the access to the CD-related H extensions will require the use of the privilege-protected IO$_DIAGNOSE > I/O function code.) You can also install the image with these B privileges. See the source for additional details - note that the H comments regarding the need for SYSGEN CONNECT are no longer applicable (at least as of VMS V5.5-2).
G There's also SYS$EXAMPLES:CDROM_AUDIO.C and .EXE, a non-Motif program, G available on OpenVMS VAX, and DECW$EXAMPLES:DECW$CDPLAYER.* on OpenVMS VAX and OpenVMS Alpha.
C The standard OpenVMS ATA (IDE) SYS$DQDRIVER device driver does not support the necessary + does not support the necessary IO$_DIAGNOSE 6 function code that is required for access to audio CD C media commands (on OpenVMS versions prior to V7.3), but an updated F SYS$DQDRIVER device driver (source code and all) with this capability & and with the source code of an updated C DECW$CDPLAYER CD audio player is available on the OpenVMS Freeware A website (www.hp.com/go/openvms/freeware/, look for the directory E /dqdriver/), and these updates are also included on OpenVMS Freeware G V5.0, and OpenVMS ECO kits containing newer versions of the driver are F available. Freeware V6.0 has a version of DQDRIVER that is newer than G that of the OpenVMS Alpha V7.3-2 release, with additional capabilities $ and with improved error diagnostics.
H OpenVMS Alpha V7.3 and later include a version of SYS$DQDRIVER with the necessary IO$_DIAGNOSE support. x 7.2 How do I access a Microsoft Windows floppy disk from OpenVMS?
A The HP Advanced Server (formerly known as PATHWORKS) for OpenVMS H product includes an unsupported and undocumented utility called PCDISK, H and this tool can read and write various Microsoft MS-DOS and Microsoft Windows FAT-format diskettes.
H ProGIS in Germany sells a product called VMove which supports DOS files C on many different device types. For more information, send mail to info@progis.de.
B Engineering Software has a product called VAKSAT which will read, G write, and erase files on MS-DOS FAT diskettes. Available for both VAX ; and Alpha. Contact ed@cityscape.co.uk for more information.
D MadGoat PC Exchange (PCX) is a utility for copying files to and from C MS-DOS and Microsoft Windows (FAT) format diskettes under OpenVMS, G using an RX23 (3.5"), RX26 (3.5"), or RX33 (5.25") diskette drive. For ; 3.5" diskettes, high-density disks can be read or written; @ double-density disks are read-only. Only high-density disks are supported on the RX33.
G The Freeware package WINFX is available on Freeware V6.0, and can read the FAT volume structure.
€F Various of the more recent AlphaStation systems use a different sound @ board (Microsoft Sound System) than the earlier DEC 3000 series systems, and G DECsound, as supplied by DECwindows Motif, doesn't support this board H nor this interface. HP offers an optional product, Multimedia Services (MMOV) for OpenVMS:
H which provides a replacement for DECsound for this card as well as many D other features (an AVI and MPEG player, video capture support, etc.)
( Ensoniq sound support is also available. f 7.4 Why is DECmigrate not working with Fortran?
|
" < %OTS-F-INDATCOR internal data corrupted in Run-time Library |
G This error can arise with Fortran programs if you are running a recent H version of OpenVMS Alpha, and are using DECmigrate to translate Fortran - applications. The DECmigrate Run-Time Library D attempts to support mixed translated-native I/O to the same unit by B sharing the native Fortran RTL's internal data structures, and in D OpenVMS 7.2 these structures changed and the translated RTL was not updated accordingly.
G You can copy DEC$FORRTL.EXE from OpenVMS 7.1, copying it to some spare H directory, and then defining the logical name DEC$FORRTL to point to it > before running your translated application. Or rebuilding the E application to use the available native Fortran compiler. Or you can < apply the current Fortran RTL kit, which has a fix for this.
H Also check for upgrades to DECmigrate (VEST and AEST) environments. See m Section 13.12 for details. For DECmigrate-related PL/I information, see 3 Section 13.3. e 7.5 How do I read IBM EBCDIC tapes on OpenVMS?
E Most (all?) IBM EBCDIC-based systems can read and write ANSI-labeled D ASCII magtapes. Fixed-length records (MOUNT /FOREIGN /BLOCKSIZE=512 H /RECORDSIZE=512, for one-block records) and the DCL COPY command can be F used to transfer fixed-record-size text files out onto tape media, or = to read from fixed-record tape media. Please consult the IBM E documentation for the details and command syntax needed when reading $ and writing ANSI media using IBM JCL * or other applicable IBM command language.
F There exists various freeware around (TAPECOPY, ETAPE, TCOPY, MTEXCH) F that can read and write EBCDIC tapes. Visit the Encompasserve (DECUS) 7 website software archives search engine and search for "EBCDIC" for details.
H OpenVMS does not include an integrated tool for EBCDIC tape processing, F but does provide a character conversion API useful within application programs.
One source for ETAPE is:
D The OpenVMS Freeware V5.0 distribution included this ETAPE tool, as well. b 7.6 How can I patch an OpenVMS Alpha image?
$ Using the OpenVMS Freeware tool ZAP:
F tell ZAP to read a block (bucket) of information based on the virtual D block number (VBN), using X for hexadecimal. Dump yourself into the G OpenVMS debugger with R2 pointing into the buffer, EXAMINE/INSTRUCTION G as needed, alter the buffer as required, GO to get out of the debugger H and back into ZAP, and use the ZAP W command to write the updated block.
B The RUN command does not accept arguments. To pass arguments to a F program, you must use what is called a "foreign command". For example:
|
" ! $ unzip :== $disk:[dir]unzip.exe $ unzip -? |
H The leading $ in the equivilence name for the symbol definition is what H makes the DCL symbol a foreign command. If the device and directory are omitted, SYS$SYSTEM: is assumed.
E Under OpenVMS V6.2 and later, DCL supports automatic foreign command F definition via the logical name DCL$PATH:. An example of a definition of this logical name is:
|
" ; $ DEFINE DCL$PATH SYS$DISK:[],ddcu:[mytooldir],SYS$SYSTEM: |
F DCL will first look for a command in the DCL command table, and if no A match is found and if DCL$PATH is defined, it will then look for E command procedures and executable images with filenames matching the H command specified, in the directories specified via DCL$PATH. The first E match found is invoked, and under OpenVMS, the DCL$PATH support will > cause a command procedure to be activated in preference to an executable image.
A For more information on foreign commands or on automatic foreign 8 command support, see the OpenVMS User's Manual.
: See also Section 10.3.
E If you want to create a detached process that takes arguments from a A command line, it must be run under the control of a command line G interpreter (CLI) (typically DCL). This is done by placing the command G line in a file, specifying SYS$SYSTEM:LOGINOUT.EXE as the image to run / and the command file as the input. For example:
|
" $ OPEN/WRITE CMD TEMP_INPUT.COM $ $ WRITE CMD "$ MYCOMMAND arguments" $ CLOSE CMD 9 $ RUN/DETACHED SYS$SYSTEM:LOGINOUT /INPUT=TEMP_INPUT.COM |
E Various OpenVMS library calls (such as lib$spawn(), cli$dcl_parse(), B and the C library system() call) require access to a command line C interpreter such as DCL to perform requested actions, and will not " operate if a CLI is not available.
D When a CLI is not available, these calls typically return the error status SS$_NOCLI. G And as mentioned above, invoke the image LOGINOUT to cause a CLI (such C as DCL) to be mapped into and made available in the context of the target process.
H For examples of how TCP/IP Services sets up its foreign commands (which B includes tools such as uuencode and uudecode), please see the DCL 8 command procedure SYS$STARTUP:TCPIP$DEFINE_COMMANDS.COM.
: Also see Section 8.10. \ 8.2 How can I clear the screen in DCL?
0 The simplest way is the TYPE/PAGE NLA0: command.
> You can set up a symbol to clear the screen in your LOGIN.COM:
|
" $ CLS :== TYPE/PAGE NLA0: |
A Your terminal must be enabled as an operator terminal before the H REPLY/LOG command can be used, but a DCL procedure (batch command file, H system startup, etc) does not have an associated terminal. To make this D work, use the following sequence to enable the OPA0: console as the ? operator terminal, then the REPLY/LOG command will be accepted:
|
" ! $ DEFINE/USER SYS$COMMAND _OPA0: $ REPLY/LOG ! $ DEFINE/USER SYS$COMMAND _OPA0: $ REPLY/ENABLE |
H To disable the system console terminal (OPA0:) as an operator terminal, use the following command:
|
" ! $ DEFINE/USER SYS$COMMAND _OPA0: $ REPLY/DISABLE |
A Also see SYLOGICALS.COM (and SYLOGICALS.TEMPLATE) for information F on configuring the behaviour of OPCOM, including the (default) use of E the system console (OPA0:) as an operator terminial and the specific D contents and behaviour of the system operator log file OPERATOR.LOG. c 8.4 How do I generate a random number in DCL?
G Here is a random number generator, just do a GOSUB RAND and the global E symbol RANDOM will contain a randomly generated number. You can feed > the generator a ceiling value (__CEIL) or a new seed (__SEED).
|
" D $! RAND - returns a positive random number ("RANDOM") between 0 and $! __CEIL - 1. $ $! sharris-at-sdsdmvax.fb3.noaa.gov $ RAND: $ $ IF F$TYPE(__SEED) .EQS. "" $ THEN . $ ! seed the random number generator, ... $ __NOW = F$CVTIME() ' $ __HOUR = 'F$EXTRACT(11,2,__NOW)' ) $ __MINUTE = 'F$EXTRACT(14,2,__NOW)' ) $ __SECOND = 'F$EXTRACT(17,2,__NOW)' ' $ __TICK = 'F$EXTRACT(20,2,__NOW)' $ B $ __SEED == __TICK + (100 * __SECOND) + (6000 * __MINUTE) + - (360000 * __HOUR) E $ ! the generator tends to do better with a large, odd seed, ... $ __SEED == (__SEED .OR. 1) $ ! clean up, ... $ DELETEX/SYMBOL __NOW $ DELETEX/SYMBOL __HOUR $ DELETEX/SYMBOL __MINUTE $ DELETEX/SYMBOL __SECOND $ DELETEX/SYMBOL __TICK $ ENDIF $ 6 $ IF F$TYPE(__CEIL) .EQS. "" THEN __CEIL = %X3FFFFFFF $ $ __SEED == __SEED * 69069 + 1 $ 8 $ RANDOM == (__SEED.AND.%X3FFFFFFF)/(%X40000000/__CEIL) $ $ RETURN |
G The MCR is an artifact of RSX compatibility mode, the operating system E from which OpenVMS is descended. MCR is the Monitor Console Routine, ? and the command is intended to activate RSX compatibility mode F utilities. When used on OpenVMS, the command is most commonly used to H run the specified image and---because the tool detects the image is not G a compatibility-mode image---it acts as a form of RUN command with the > default file specification of SYS$SYSTEM:.EXE. MCR passes any D (optional) command line arguments in a fashion similar to a foreign command. In other words:
|
" $ MCR FOO BAR |
is equivalent to:
|
" $ FOO :== $FOO $ FOO BAR |
@ MCR is not documented. Use of a foreign command or the DCL$PATH ` mechanism is preferred. For details on this, see Section 8.1. d 8.6 How do I change the OpenVMS system prompt?
E You can use the SET PROMPT command for this purpose. SET PROMPT sets ' the DCL prompt to the specified string.
@ When you want to display variable information, you will need to C establish a tie-in that provides the information to the SET PROMPT command as required.
D If you wish to display the default directory for instance, you will D have to establish a tie between the SET DEFAULT command and the SET H PROMPT commands, as there is no direct way to get the default directory A as the DCL prompt. You can easily acquire or create a set of DCL H command procedures that perform the SET DEFAULT and SET PROMPT for you. 9 These DCL command procedures often use a command such as:
|
" ( $ set prompt='f$environment("default")' |
> More advanced users could implement a system service or other E intercept, and use these tools to intercept the directory change and B reset the prompt accordingly. (This approach likely involves some > kernel-mode programming, and requires write access to various & undocumented OpenVMS data structures.)
F There are related tools available from various sources, including the following web sites:
Yes, you can do this with DCL.
E The OpenVMS DECnet documentation shows various simple examples using G the task object and the TYPE command to trigger the execution of a DCL E command procedure on a remote node. An example DCL command procedure F that is rather more advanced than using the TYPE command as a trigger ' is included in the Ask The Wizard area:
H For additional information on the OpenVMS Ask The Wizard (ATW) area and B for a pointer to the available ATW Wizard.zip archive, please see 0 Section 3.9.
D DCL does not include support asynchronous I/O, thus a predetermined C protocol or a predetermined "turn-around" command sequence must be D implemented in order to avoid protocol deadlocks---cases where both E tasks are trying to write or both tasks are trying to read. The task G that is writing messages to the network must write (or write and read) F a predetermined sequence of messages, or it must write a message that F tells the reader that it can now start writing messages. (This is the 8 essence of a basic half-duplex network protocol scheme.) h 8.8 How can I get the width setting of a terminal?
|
" ) $ width = f$getdvi(terminal,"DEVBUFSIZ") |
@ Use DCL ampersand substitution, and not apostrophe substitution.
|
" D $ pipe show system | search sys$input opcom | (read sys$input pid ; A pid=f$element(0," ",pid) ; define/system opcom_pid &pid) $ show log opcom_pid 0 "OPCOM_PID" = "0000020B" (LNM$SYSTEM_TABLE) |
4 With a command to create a detached process such as:
|
" 9 $ RUN/DETACHED SYS$SYSTEM:LOGINOUT /INPUT=TEMP_INPUT.COM |
B If you are trying to use a logical name as the /INPUT, /OUTPUT or D /ERROR on a RUN/DETACH command, then you must translate the logical G name specifications to physical references before passing them, or the G definitions must reside in a logical name table that is visible to the newly-created process.
F Also note that LOGINOUT only creates the SYS$LOGIN, SYS$LOGIN_DEVICE, and SYS$SCRATCH J logical names if it is processing a login that is based on the contents G of a SYSUAF record---without access to the associated SYSUAF record, E this information is not available to LOGINOUT. (If you want to see B these particular logical names created, then please specify the 4 /AUTHORIZE qualifier on the RUN/DETACHED command.)
G If you do not specify LOGINOUT as the image, then there is no easy way E to get these logical names. Also, any logical names that are used in C the target image file specification must also be in a logical name E table accessible (by default) by the newly-created detached process. C Shared tables include the group (if the process is in the same UIC H group) and the system table. (If the target process is to be in another E UIC group, a suitablly privileged user or application can create the C necessary logical name(s) directly in the other group logical name table.)
H When in doubt, create a short DCL command file as input, and use a SHOW G LOGICAL and similar commands to examine the context. (And use physical B device and directory references on the RUN/DETACH of the LOGINOUT F image, when specifying this command file as /INPUT.) Also remember to H check both security auditing and system accounting when troubleshooting problems with the RUN/DETACH.
8 Also see Section 8.1. l 8.11 How to use escape and control characters in DCL?
4 To write a message and then the bell character, use:
|
" $ bell[0,7] = 7 " $ write sys$output "Hello''bell'" |
To write blinking text, use:
|
" $ esc[0,7] = 27 $ text = "Blinking Text" . $ write sys$output "''esc'[5m''text'''esc'[m" |
u Also see sections Section 11.6, Section 12.1.
| Previous | YNext | \Contents | ^Index |