Re: where to find docs on Display/Alter/Dump in STRSST??? (How to dump an OPM RPG program object?) -- MI400

Hello Dan,

You wrote:
>Trying to figure out how to dump a program object using STRSST's
>Display/Alter/Dump.  "Help" is not, pointing inquiring minds to "See the
>System Diagnostic Aids Manual (LY44-0597) for more information about this
>service tool."  I have searched high & low for this manual with no success.

The LY manuals are licenced and must be specifically ordered.  If I recall
correctly, they are only available if IBM show you as having a licenced copy
of the operating system.

>I'd appreciate it if someone could provide me with a *WORKING* link (IBM's
>docs provide links to this manual in various releases, but they're all dead
>links).

Ain't no such thing ... see reason above ... while on-line links to the LY
manuals probably exist I suspect you have to be inside the IBM firewall to
access them.

>Otherwise, if it does not exist, could someone tell me how to dump an OPM
>RPG program object?  The prompts ask for one of the following:

Object is the object name (i.e., program).  A context is effectively
equivalent to a library (so called because it provides a reference to the
object i.e., a context).  As most AS/400 people know, QSYS is a special
library because it can contain libraries as well as objects that don't have
a library (e.g., user profiles).  QSYS is the external representation of the
machine context.  The machine context is used to locate everything else
(except those objects with fixed addresses, and temporary objects for which
the pointer returned when the object is created is needed).  DMPSYSOBJ
allows you to refer to the machine context via the *MCHCTX special value.
However, QSYS is not the same as the machine context -- run DMPSYSOBJ and
see that some objects in the list of pointers (.POINTERS) are explicitly
located in the QSYS library, others are located in the MACHINE CONTEXT**.

>* Find By Object Name And Context Name
>   Object:
>     Type . . . . . . . . . :   (02) - Program
>     Name . . . . . . . . . .   ______________________________
>     Subtype  . . . . . . . .   01   00-FF


Type the program name.  The subtype is a little trickier.  OPM and ILE
programs are subtype 01, SQL packages are subtype 02, service programs are
subtype 03.  You can find the internal type and subtype for external objects
by calling the QLICVTTP API.  For internal object types you must dump the
object and read the dump -- unless you want to work out how to call QLICNV.

>  Context:
>     Name . . . . . . . . . .   ______________________________
>     Subtype  . . . . . . . .   01   00-FF

Type the library name.  The subtype for permanent libraries is 01, for
temporary libraries (i.e., QTEMP) is is C1.

>* Find By Object Address
>   Object address . . . . . .   00000000 0000

Use this when you know the address of the object such as certain
fixed-address internal system structures, or temporary objects.  Usually you
need to dump some other object (e.g., QTEMP) to find the address.

** To see all the various objects on the system you can dump the machine
context.  For example:
        DMPSYSOBJ OBJ(*ALL) CONTEXT(*MCHCTX)
(although submitting it to batch would be a good idea).  Note that this will
generate a spooled file with 10's of thousands of pages!

Regards,
Simon Coulter.

--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists
   http://www.flybynight.com.au/

   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------