Net Print/400 - Installation

This chapter provides an explanation of the process for installing I/NET Net Print/400 on your AS/400. It will also tell you how to install the permanent license key for the product.

The installation process will use the RSTLICPGM command to install the product, in a similar fashion to other products for the AS/400. The product identifier for Net Print/400 is 7NETPRT.

Net Print/400 is protected with a license key. You will have a 30 day grace period from the time you transmit your first report using the product. Messages will be sent to the system operator's message queue each time a report is sent without a permanent license key. These messages will inform you that you are running a product that does not have a permanent license key. The number of days left to use the product in the grace period will also be shown.

To use Net Print/400 beyond the 30 day grace period, you will be required to obtain a license key from the distributor of the product.

Before You Begin Installation

Before you install Net Print/400, you should review and perform the following:

Net Print/400 uses functionality provided by version 2.0 of Webulator/400, or an HTTP server like Commerce Server/400 or the Netscape Enterprise Server for the IBM AS/400. One of these supported products should be installed on your AS/400 prior to the first attempt to execute any Net Print/400 functions.

Webulator/400 requires specialized PTF's to allow for the transmission of the Net Print/400 data to the browser. You should receive and install PTFs WBL200017 and WBL200018 to transmit a report using Net Print/400. PTFs for Webulator/400 may be found via the I/NET support web pages at the following URL:

	 	 

http://www.inetmi.com/iseries/support

Net Print/400 uses OS/400 functions that are available in V3R2 (on IMPI systems) or V3R7 and above (on RISC systems). The product will not install or work properly at previous levels. As a result, you should proceed with the installation at those levels or higher only. The latest PTFs for OS/400 and TCP/IP should also be installed prior to executing any of the product functions.

Appropriate configurations should be put in place for the desired server to call the Net.Data CGI interface to Net Print/400. In addition, the Web Server/400 PTF WWW130021 is required to execute Net.Data macros.

Net Print/400 uses functionality found in a browser plug-in. An appropriate browser should be installed at the client machine (PC) to utilize this plug-in functionality. Browsers that have been tested as of this writing include Netscape Communicator version 3.x and 4.x Microsoft Internet Explorer version 4.x and version 5.x.

If you need additional information on accomplishing these tasks, or the contents included in the following sections, consult your system administrator or contact your product support organization.

Installation Instructions

Summary

The following section summarizes the installation of Net Print/400.

Review the License Agreement that accompanies the Net Print/400 package.
Place the distribution CD or tape into the appropriate AS/400 drive. If the product is delivered in an AS/400 save file, this step can be eliminated.
Sign on as a user who has *SECOFR user class. This user must also exist in the system distribution directory.
Install the product by using the RSTLICPGM command.
Make any changes or movements to product samples desired.

Detail

The following section gives detailed instructions for the installation of Net Print/400.

Review the License Agreement that accompanies the Net Print/400 package.
A printed copy of the license agreement is included in the product package or may be requested by contacting your software vendor or I/NET If you do not accept the license agreement, you should not continue with the installation. If you continue, it is assumed that you have accepted, and will abide by, the contents of the license agreement.
Place the distribution CD or tape into the appropriate AS/400 CD drive or tape drive. If the product is delivered in an AS/400 save file, this step can be eliminated.
Sign on as a user who has a *SECOFR user class.
Since the Net Print/400 product includes objects installed in the shared folders (QDLS) file system, the user performing the installation must also exist in the system distribution directory. It may be necessary to add this user with the Add Directory Entry (ADDDIRE) command.
Install the product using the standard AS/400 licensed program installation routines. Enter the command:
RSTLICPGM LICPGM(7NETPRT) DEV(xxxx).The xxxx refers to the specific name of the CD or tape device where the product will be installed from. Typically this will be either OPT01 or TAP01 depending on whether you are installing from CD or from tape. If the product is to be installed from an AS/400 save file, this will be *SAVF and the SAVF (save file and library) parameter must include the save file that contains the product.
Note: This process will take longer than usually expected when installing the product on an AS/400 running OS/400 V3R2. This is a result of OS/400 re-encapsulating the executable objects from a RISC to IMPI state.
Make any changes to the supplied sample objects.
Sample objects are installed as part of the Net Print/400 product. It is possible to duplicate and modify them in another area of the system for customization purposes.

Install Command and Parameter Descriptions

License Program/Product
This is the licensed program product number being installed. 7NETPRT for the complete Net Print/400 product.

Release
This is the product's release level in Version, Release and Modification Level format. The current release available for Net Print/400 is V1R0M0, but it is appropriate to allow the Release value to default to *FIRST on the RSTLICPGM command.

Primary NLV of this System / Language for Licensed Program
This is the primary NLV (National Language Version) of the AS/400 that this product is being installed onto. This information is used to determine which version of language objects to install. The default RSTLICPGM command value *PRIMARY should be used for the installation of Net Print/400.

Install Product into Library / Library 1-n
This is the library where the programs, service programs and other objects will be placed during the RSTLICPGM (Restore Licensed Program) process. If the library exists, the objects will be placed into that existing library. If the library does not exist, it will be created for you. The default is if nothing is entered is NETPRTINET. It is recommended to use this default. Throughout the documentation, this value will be referred to as the "product library".

Install Home Folder / Folder
This is the Shared Folders /QDLS directory to which all IFS (Integrated File System) directory type objects will be installed. This directory may already exist and will reside within the QDLS (shared folders) file system. If it doesn't exist, it will be created. It is recommended to let the RSTLICPGM portion of the install process create the default folder (NPW) for you. The installation process will install macro, plug-in and documentation objects into this QDLS directory tree and may also be accessed via the IFS root in the /QDLS/NPW directory.

Net Print/400 User Profile
This is the name of the user profile that owns all of the objects that are shipped to you in the product. If this profile name does not already exist, it will be automatically created during the installation process. The owner name is NPWUSER. You do not have the ability to change this owner.

This profile is automatically created with a user class of *USER and no special authorities granted. It is also created with no password and has an initial status of *DISABLED. In addition, a system distribution directory entry will also be created automatically with the Add Directory Entry (ADDDIRE) command for the product user profile.

What the Installation Process Does

The installation process is centered around execution of the RSTLICPGM (Restore license program) command.
The installation process will begin with a pre-install exit program creating the product user profile NPWUSER (if it doesn't already exist).

Since the product includes objects in the QDLS directory tree, a system distribution directory entry will then be added within the pre-install exit program for the new product user profile. If the product is later removed (using the DLTLICPGM command) the user profile and directory entry are not automatically deleted, and should be removed manually.

Next, mainstream logic in the RSTLICPGM command will do the physical installation of the products. The option installed is the *BASE option.

The RSTLICPGM command will create the product library (if it doesn't exist) and will create the home folder (if it doesn't exist). By default, the product library is NETPRTINET and the home folder is NPW.

The product library includes all the programs, commands, and other objects necessary for the operation of Net Print/400. It is important to note that Machine Readable Interface (MRI) objects are not duplicated in system libraries. As a result, the product library must be in the library list whenever executing or using Net Print/400 objects.

The install home folder (typically NPW) contains the macros and documentation for the product. A version of the browser plug-in is also installed here, although the plug-in may also be available by contacting your product vendor or via download from the I/NET website at the following URL for assistance:

http://www.inetmi.com/iseries/netprint

The following folders/directories are created under the home folder.

pubs contains the product publications and documentation (available in multiple formats).

plugin contains the product plugins to be used in the browser.

macros contains the Net.Data macro files that are used to help provide CGI capabilities for the selection of reports to be printed.

While these objects can be used from where they are installed, it is advisable to actually copy them from to another IFS directory. This is for both efficiency and customization purposes. As a result, the contents of these areas should be duplicated by the user to another directory for actual use, as they may be deleted or over-written in the future. For more information about macro customization, refer to the "Processing a Report using a Net.Data macro" in chapter 5.

Obtaining and Installing the License Key

This product is protected with a software license key. The key is managed using the built-in IBM AS/400 license management procedures.

To obtain a key, contact your product distributor, or see the I/NET website at the following URL for assistance:

http://www.inetmi.com/iseries

Current instructions will also be provided at the web site.

To Install the Licensed Key:

Key in WRKLICINF PRDID(7NETPRT). (See Figure 2.1).
Key in a 1 next to the I/NET Net Print/400 product and press Enter.
The prompt for the ADDLICKEY command (Figure 2.2) will be shown.
Key the authorization characters you were provided into the LICKEY (License key) parameter and change the usage limit (USGLMT parameter) to *NOMAX. Press Enter.

Your product is now permanently authorized.

The following figures show the referenced examples of the resulting WRKLICINF display and ADDLICKEY command prompt. Please refer to the OS/400 CL Reference (Document Number SC41-5722) or the Security - Reference guide (Document Number SC41-5302) for additional help topics.

Figure 2.1 Step 1 for Licensed Key Installation

                     Work with License Information                    SYSNAME
                                                             01/01/99 10:10:00

System serial number . . . . . . . . . :   9999999
Processor group . . . . . . . . . . . :   P05

Type options, press Enter.
  1=Add license key 2=Change 5=Display detail 6=Print detail
  8=Work with license users ...

License
Opt  Product   Term    Feature  Description
1   7NETPRT   V1R0M0  7000     I/NET Net Print/400

                                                                        Bottom
Parameters or command
===>
F3=Exit F5=Refresh F11=Display Usage Information F12=Cancel
F17=Position to F23=More options

Work with License Information SYSNAME 01/01/99 10:10:00 System serial number . . . . . . . . . : 9999999 Processor group . . . . . . . . . . . : P05 Type options, press Enter. 1=Add license key 2=Change 5=Display detail 6=Print detail 8=Work with license users ... License Opt Product Term Feature Description 1 7NETPRT V1R0M0 7000 I/NET Net Print/400 Bottom Parameters or command ===> F3=Exit F5=Refresh F11=Display Usage Information F12=Cancel F17=Position to F23=More options

The initial WRKLICINF display does not include any distinctive information concerning the existence of license key information for any displayed products. You may wish to use the F11 option or specifically display the license information detail for the Net Print/400 product to ensure key and usage limit information existence prior to execution of the ADDLICKEY command in the following example.

The product is not licensed based on user or usage limits, so the maximum value (*NOMAX) is appropriate to provide the site / machine licensing required. If another value is used during the addition of the license keys, unpredictable results may occur.

Figure 2.2 Step 2 for licensed key installation

                  Add License Key Information (ADDLICKEY)

Type choices, press Enter.

License key input . . . . . . . > *PROMPT       *PROMPT, *LICKEYFILE, *TAPE
Product identifier . . . . . . . > 7NETPRT       Identifier
License term . . . . . . . . . . > V1R0M0        Vx, VxRy, VxRyMz
Feature . . . . . . . . . . . . > 7000          5001-9999
System serial number . . . . . . > 9999999       Number, *LOCAL, *REMOTE,*ALL
Processor group . . . . . . . . *ANY          Character value, *ANY
License key:
Characters 1 - 6 . . . . . . . .>  XXXXXX        Character value
Characters 7 - 12 . . . . . . .>  YYYYYY        Character value
Characters 13 - 18 . . . . . . .>  ZZZZZZ        Character value
Usage limit . . . . . . . . . .>  *NOMAX        0-999999, *NOMAX
Expiration date . . . . . . . .   *NONE         Date, *NONE
Vendor data . . . . . . . . . .   *NONE         Character value, *NONE

                                                                        Bottom
F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display
F24=More keys

Add License Key Information (ADDLICKEY) Type choices, press Enter. License key input . . . . . . . > PROMPT PROMPT, LICKEYFILE, TAPE Product identifier . . . . . . . > 7NETPRT Identifier License term . . . . . . . . . . > V1R0M0 Vx, VxRy, VxRyMz Feature . . . . . . . . . . . . > 7000 5001-9999 System serial number . . . . . . > 9999999 Number, LOCAL, REMOTE,ALL Processor group . . . . . . . . ANY Character value, ANY License key: `Characters 1 - 6 . . . . . . . .>` XXXXXX Character value Characters 7 - 12 . . . . . . .> YYYYYY Character value Characters 13 - 18 . . . . . . .> ZZZZZZ Character value Usage limit . . . . . . . . . .> NOMAX 0-999999, NOMAX Expiration date . . . . . . . . NONE Date, NONE Vendor data . . . . . . . . . . NONE Character value, *NONE Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys

The product includes an automatic 30 day trial period for use without activation or licensing. If extended trial use is necessary, an extended license may be granted. Addition of this type of license key is identical to the process used to add a permanent key, with the exception that an Expiration date will be required for the extended license. This date will be provided by the distributor of the temporary key and should be entered on the ADDLICKEY command in system date format.

Troubleshooting Installation

If any problems are detected during the installation, you will be presented with a system error message indicating the source of the problem. Many of these messages will directly indicate the recovery action necessary to resolve the problem and continue the installation. If you are not able to determine the problem, please contact your system administrator or product support organization.

Common Problems:

I received the message CPF3D96 indicating Objects for product 7NETPRT option *BASE release V1R0M0 not restored during the RSTLICPGM process.
This message is usually accompanied by the messages CPF3743, CPD3DC1 and CPD3DFD. These messages all allude to an attempt to install the product on an OS/400 version that is not supported, typically pre-V3R2 or pre-V3R7. Make sure your AS/400 operating system is running at V3R2 for IMPI machines or at V3R7 and above for RISC machines before attempting the RSTLICPGM command again.

The user QDFTOWN owns all the objects installed for the product.
You typically see the messages CPF3723, CPF90A2, CPF9064 and CPF90A1 in the installation job log when this situation occurs. This is a result of errors encountered in the pre-install exit program process, possibly relating to authorities of the user issuing the RSTLICPGM command preventing the creation of the NPWUSER product user profile. Delete the product using the DLTLICPGM command, make sure that the user profile you are signed on as has *SECOFR authorities, and reinstall the product.

The user QDFTOWN owns all the folder (QDLS) objects installed for the product.
Receiving the message CPF9006 during the RSTLICPGM process is also associated with this situation. You may also see the messages CPF90A2, CPF9064 and CPF90A1 in the installation job log. This is a result of errors in the pre-install exit program process, possibly relating to the existence of the user issuing the RSTLICPGM command in the system distribution directory. The NPWUSER product user profile was probably not added to the system distribution directory. Delete the product using the DLTLICPGM command, make sure that the user who is signed on is in the system distribution directory, and reinstall the product.

I received the message CPD9032 or CPD1075 when I attempted to install the product.
You are not signed on to the AS/400 as a user who has *SECOFR user type authorities. As a result, you are not authorized to execute the RSTLICPGM command. Another possibility is that you have limited capabilities associated with your user profile. Sign on as a different user or obtain sufficient authorities to execute the commands to install the program product before continuing.

I received the message CPD3DC1 or CPF9006 when I attempted to install the product.
You are not signed on to the AS/400 as a user who is enrolled in the system distribution directory. As a result, you are not authorized to install objects into the shared folder (QDLS) file system. Sign on as a different user or add the user to the system distribution directory before continuing. Adding the entry may be accomplished by using the ADDDIRE command. You may also wish to consult your system administrator or the OS/400 CL Reference (Document Number SC41-5722) for additional information about system distribution directory entries and their relationship to the installation of licensed programs.

I received a CPF message when I attempted to license the product.
Generally, the message responses from the license key functions contain sufficient explanation to resolve any issues that may exist. Typical errors that you might be able to expect would result from serial number or license key data transpositions, or an invalid usage limit specification. Another possibility includes entering the license expiration date for a temporary key in the wrong date format - it must be entered according to the date format of your AS/400 job. You also may not be signed on to the AS/400 as a user who has *SECOFR user type authorities. If the Net Print/400 product is not included on the list when performing the WRKLICINF command, it is also possible that a product ID or release level transposition has taken place. Verify all of your data before attempting the license request again.

The RSTLICPGM is taking a long time and the CPU on my AS/400 is also running very high.
The RSTLICPGM process will take longer when first time installing. What is usually expected depends on many variables. When installing the product on an AS/400 running OS/400 V3R2. This is a result of OS/400 re-encapsulating the product's executable objects from a RISC to IMPI state. The re-encapsulation functionality also requires a substantial amount of CPU activity.