Discovering WebDocs-dependent custom applications

From Support

This knowledge base article is intended to be used in conjunction with a WebDocs iSeries library upgrade, particularly with a jump from the 2.x to 3.x versions.

Contents 1 BEFORE THE UPGRADE 1.1 Step 1: Find dependent logical objects 1.2 Step 2: Find source files 1.3 Step 3: Check default exit programs 1.4 Step 4: Find programs that use WebDocs objects 1.5 Step 5: Delete logical objects 2 AFTER THE UPGRADE 2.1 Step 1: Recreate Logical Files 2.2 Step 2: Recompile applications 2.3 Step 3: Test

BEFORE THE UPGRADE

Prior to running the WebDocs library upgrade, use the following steps to discover what objects exist that reference WebDocs files, and whether they need to be modified or recompiled.

Step 1: Find dependent logical objects

List the physical file objects in the RJSIMAGE library.

WRKOBJPDM RJSIMAGE OBJATR('PF-DTA')

We will check to see if we have the Display Database Relations PDM option (DD) available.

F16 Work with User-Defined Options

If DD PDM option does not already exist, we'll create it.

F6 Create User-Defined Option

Option: DD

Command: DSPDBR FILE(&L/&N)

Back at the Work with Objects using PDM screen, key DD on the first entry, and then hit F13 to repeat the option for all the physical file objects.

DD
F13
Enter

Examine the logical file names in the DSPDBR display. Note any files or dependent files that do not exist in the RJSIMAGE library, or do not have a DOC prefix.

Step 2: Find source files

If any logical files are noted from the process above, we need to run this command for each to determine where their source files are located:

DSPOBJD OBJ(LIBRARY/LOGICALFILE) OBJTYPE(*FILE) DETAIL(*SERVICE)

Note in a spreadsheet or other document the logical file and the associated source library and source name used to create it. We will reference this following the upgrade.

Step 3: Check default exit programs

Prompt on the WebDocs check-in command to check the default exit programs:

RJSIMAGE/DOCCHKIN
F4

Page down until you see where the Pre Check-in exit program and Post Check-in exit program and their libraries are referenced.

If your settings differ from the defaults noted in the image below, please record them. You will need to run the CHGCMDDFT command following the upgrade to change the DOCCHKIN back.

Repeat for the following three commands:

RJSIMAGE/DOCINFOUPD

RJSIMAGE/DOCFLOWAPC

RJSIMAGE/DOCFLOWREJ

Step 4: Find programs that use WebDocs objects

Determine which programs are using objects from RJSIMAGE. For each library that holds source members for RPG or CL programs, run the following commands:

WRKMBRPDM FILE(LIBRARY/SOURCEFILE)

Put a 25 on the first entry, and F13 to have it copy down to all members.

25
F13

We are going to try to find the string 'doc' and hit enter. We are going to try to find any files with a DOC prefix that are being referenced in your source. Of particular concern are matches in the F-specs or C-specs. Please be aware that this may return some false positives.

Note the programs that have a match in the F- or C-specs.

Step 5: Delete logical objects

Delete the logical objects identified above from their respective libraries.

DO NOT DELETE THE SOURCE OBJECTS & LIBRARIES FOR THE LOGICAL FILES

AFTER THE UPGRADE

Step 1: Recreate Logical Files

Recreate the logical files discovered prior to the upgrade. In the command below, for every logical file discovered in the process above:

• Replace OBJLIB/LOGICAL with the library and object name noted.
• Replace LOGSRCLIB/LOGSRCFILE with the source name and library noted.

CRTLF FILE(OBJLIB/LOGICAL) SRCFILE(LOGSRCLIB/LOGSRCFILE)

Step 2: Recompile applications

Recompile the RPG & CL members discovered prior to the upgrade into their respective libraries.

Step 3: Test

Test your applications and contact Technical Support if you have any questions or concerns.

This article has been proofread by Jordan as of 11:05, 16 April 2008 (Central Daylight Time)