HP OpenVMS systems documentation

You can include prompt text in your PTF using the =prompt directive. Prompt text cannot exceed one line of text. (The suggested line length is 60 characters.) Help text is similar to prompt text, except that it can span multiple lines. The help text follows the =prompt line. You can also include blank lines in help text.

The following example shows prompt text:

=prompt This option provides files for programming support.

The following example shows a sample product text file. Note the prompt and help text:

=product HP VAXVMS UCX V2.0 full 1 'PRODUCT =prompt HP TCP/IP Services for OpenVMS HP TCP/IP Services for OpenVMS is an OpenVMS layered software product that promotes interoperability and resource sharing between OpenVMS systems, UNIX systems, and other systems that support the TCP/IP and NFS protocol suites. The product provides capabilities for file access, remote terminal access, remote command execution, remote printing, mail, and application development, including three major functional components: o The Run-Time component, which is based on the Berkeley Standard Distribution, brings TCP/IP communications to OpenVMS computer systems. It also includes a suite of application development tools (DECrpc, C socket programming interface, and QIO programming interface). o The Applications component includes the popular user-oriented protocols for file transfer, remote processing, remote printing, and mail: File Transfer Protocol (FTP), Telnet Protocol (Telnet), Berkeley R commands (rsh, rlogin, rexec), remote printing, and Simple Mail Transfer Protocol (SMTP). o The HP NFS component supports Network File System (NFS) V2.0 proto- col specifications. NFS is an Application layer protocol that provides clients with transparent access to remote file services. 1 'NOTICE =prompt Copyright 2003 Hewlett-Packard Company. All rights reserved. Unpublished rights reserved under the copyright laws of the United States. This software is proprietary to and embodies the confidential technology of Hewlett-Packard Company. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from HP or an authorized sublicensor. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19 or in FAR 52.227-14 Alt. III, as applicable. 1 'LICENSE =prompt This product uses the PAKs: UCX and UCX-IP-RT. This product currently has two Product Authorization Keys (PAKs): Producer PAK Name Version Release Date DEC UCX 2.0 6-JUL-1992 DEC UCX-IP-RT 2.0 6-JUL-1992 1 'PRODUCER =prompt Hewlett-Packard Company This software product is sold by Hewlett-Packard Company. 1 EXAMPLES =prompt Example files The example files include client/server programming examples. 1 NFS =prompt NFS files The HP NFS component supports Network File System (NFS) protocol specifications. NFS is an application layer protocol that provides clients with transparent access to remote file services. The HP NFS server promotes data sharing among clients by providing a central data storage facility for OpenVMS and UNIX files. The HP NFS server provides two types of file access for UNIX clients: 1) client access to OpenVMS files, and 2) client access to files compatible with UNIX systems. 1 APPLICATIONS =prompt Applications The Applications component includes the popular user-oriented protocols for file transfer, remote processing, remote printing, and mail: File Transfer Protocol (FTP), Telnet Protocol (Telnet), Berkeley R commands (rsh, rlogin, rexec), remote printing, and Simple Mail Transfer Protocol (SMTP). 1 PRE_INSTALL =prompt Complete preinstallation tasks for HP TCP/IP Services first. Before you install HP OpenVMS UCX, you must complete certain preinstallation tasks. For more information, refer to the "HP TCP/IP Services for OpenVMS Installation and Configuration Guide." 1 POST_INSTALL =prompt Postinstallation tasks required for HP TCP/IP Services. For more information, refer to these associated documents: - "HP TCP/IP Services for OpenVMS Installation and Configuration Guide" - "HP TCP/IP Services for OpenVMS System Management"

Use the PRODUCT PACKAGE command to create a software product kit. This operation uses a product description file (PDF), an optional product text file (PTF), and product material files as input to produce a software product kit in either sequential or reference format.

The syntax of the PRODUCT PACKAGE command is documented in the HP OpenVMS System Management Utilities Reference Manual.

This chapter shows you how to create a product kit in sequential format from product materials that are spread across several directories. A game application named CHESS is used throughout this chapter to illustrate the steps required to package the kit. You will also be introduced to the PRODUCT LIST, PRODUCT EXTRACT, and PRODUCT COPY commands, which are useful for manipulating the product kit.

Assume that the files needed to package the CHESS product have been organized into a directory tree. The following is a listing of this directory tree containing the product material, required kitting files, and other files produced by the engineering team (such as listing and object files).

$ DIRECTORY /COLUMN=1 /NOTRAILING DKA300:[TEST.*] Directory DKA300:[TEST.COM] CHECK_SPACE.COM;1 CHESS_IVP.COM;1 Directory DKA300:[TEST.KIT] CHESS.PCSI$DESC;1 CHESS.PCSI$TEXT;1 PACKAGE.COM;1 Directory DKA300:[TEST.LIS] CHESS.LIS;1 Directory DKA300:[TEST.OBJ] CHESS.EXE;1 CHESS.OBJ;1 Directory DKA300:[TEST.SRC] CHESS.C;1 CHESS.GAMES;1 CHESS.OPENINGS;1 HEADER.H;1

5.1 Description of the Product Material

The product material for the CHESS application consists of the files that will be installed on the user's system along with any command procedures included in the kit to perform product-specific tasks during installation.

Assume that the product material is located in the directory tree [TEST...] as follows:

• An executable image named CHESS.EXE is located in [TEST.OBJ]. It will be placed in [SYSEXE] on the target disk when the product is installed.
• Two data files, CHESS.OPENINGS and CHESS.GAMES, reside in [TEST.SRC]. The first file, an opening book, will always be copied to [SYSEXE] on the user's system. However, the second file, a large games collection, is an optional component of the product. Users determine at install time whether or not to install this file. If they choose not to install it, they can later reconfigure the product to obtain this optional file.
• Two command procedures, CHESS_IVP.COM and CHECK_SPACE.COM, are placed in [TEST.COM]. CHESS_IVP.COM will be copied to [SYSTEST] on the destination device and executed to verify the correct installation of the product. CHECK_SPACE.COM will be executed early during the installation but it will not be left on the user's system. It checks for adequate space on the destination device for large work files that will be used when the product is used.

The contents of the two command procedures from [TEST.COM] are shown here as they might appear early in the packaging process. Later in the development cycle they will be replaced by command procedures that perform their intended functions.

$ TYPE [TEST.COM]*.* DKA300:[TEST.COM]CHECK_SPACE.COM;1 $! This command procedure is executed from an EXECUTE PRECONFIGURE statement $! with the INTERACTIVE keyword specified. Therefore, all output lines $! generated will be displayed. $! $ write sys$output "*** Output from execute preconfigure ***" $ exit 1 DKA300:[TEST.COM]CHESS_IVP.COM;1 $! This command procedure is executed from an EXECUTE TEST statement without $! the INTERACTIVE keyword specified. Therefore, only output lines that $! look like an OpenVMS message (that is, those starting with %) will be $! displayed. By default, all other output from this $! procedure will be suppressed unless the /TRACE qualifier is used on the $! PRODUCT INSTALL command. For testing purposes you can force a line $! of text to be displayed by putting a percent sign in column 1. $! $ write sys$output "%%% Output from execute test %%%" $ exit 1