pdbl - set up and manage user-specific program cache

Any user can call this command. This command enables the current user to set up, maintain and manage user-specific program caches. There are two scope types for user-specific program caches:

SESSIONWIDE

all the processes of a session are connected

USERWIDE

all the processes of a user ID are connected

Syntax

pdbl{ -s[ sid]| -u} -i

pdbl{ -s[ sid]| -u} -e size

pdbl{ -s[ sid]| -u}{ -a| -d}

pdbl{ -s[ sid]| -u} -D

pdbl{ -s[ sid]| -u} -b path

pdbl{ -s[ sid]| -u} -l[ element]

pdbl{ -s[ sid]| -u} -r element

pdbl -h

options

-s sid

The program cache of a session (SESSIONWIDE scope) is selected. sid is the ID of the desired session. If sid is not entered, the current session will be automatically selected.

If the option -s is selected, all the following options operate on the program cache of the selected or current session.

-u

The program cache of the user ID (USERWIDE scope) is selected.

If the option -u is selected, all the following options operate on the program cache of the current user.

-i

The status of the program cache and statistical data about size and allocation percentages is written to standard output in the following format:

Cache name            CREATED: date time    STATE: status                       
                      SIZE: zize   MB      ENTRIES: entries
                      FREE PAGES: pages

name

The name of the program cache is formed with the letters DBL, the scope (S for SESSIONWIDE or U for USERWIDE) and the corresponding ID of the session or the user. For example, the program cache of session 504 has the name DBLS504.

date

Date of program cache set-up.

time

Time of program cache set-up.

status

Current status of program cache (active, inactive or in delete).

size

Total cache size in megabytes.

entries

Current number of stored core images.

pages

Number of memory pages still available in cache. In the worst case, there is one memory page less available to core images because the extension of the cache catalog occupies one page.

-e size

The program cache is set up and activated in the size indicated (in megabytes). The maximum size of the cache is not determined by pdbl but by system- and task-specific settings. The size of the cache cannot exceed the ADDRESS-SPACE-LIMIT of the user ID.

-a

The program cache is activated and used immediately in loading processes.

-d

The program cache is deactivated and ignored immediately in loading processes.

The program cache is resolved if no currently stored core images are present (this is analogous to option -D). The program cache remains in the inactive status if core images are still present.

-D

The program cache is resolved and no longer used in loading processes.

If the program cache is locked because the loading process has already started, it will remain in the in delete state until all current loading processes have been finished.

-b path

The core image of a program identified by its path is stored in the program cache. The program entered under path must be executable.

-l

A list of all core images currently stored in the program cache is written to standard output in the following format:

element size date time library

element

Name of the program element in the PLAM library or the plain file name of the program in UFS.

size

Number of memory pages occupied by the core image.

date

Date of the last access to the core image.

time

Time of the last access to the core image.

status

Current status of the program cache (active, inactive or in delete).

library

Name of the PLAM library from which the core image was loaded or the path name of the LLM in UFS.

-l element

Detailed information about the core image element in the program cache is written to standard output in the following format:

element          CREATED : cdate ctime     ACCESS: adate atime                  
                 START AT: staddress        CACHESIZE: csize kB
                                            USECOUNT: number
                 -----------------------------------------------
                 SLICES  : sl LOADADDR:     SIZE:
                              loaddress     ssize kB
                              . . . . .     . . . . .
                 -----------------------------------------------
info

Meaning of output

element

Name of the program element in the PLAM library or the plain file name of the program in UFS.

cdate

Creation date of the core image.

ctime

Creation time of the core image.

adate

Date of the last access to the core image.

atime

Time of the last access to the core image.

staddress

Start address of the core image during processing.

csize

Number of kilobytes occupied by the core image.

number

Number of load accesses to the core image.

sl

Number of slices. 

loaddress

Load address of the slices.

ssize

Number of kilobytes occupied by the slices.

info

Information about the core image origin.

-r element

The core image element will be deleted from the program cache. All core images of the program cache will be deleted if "*" is indicated as an element.

-h

An overview of all options and parameters is given.

Example

# pdbl -u -e 16        # set up program cache
# pdbl -u -i           # show status
Cache DBLU101          CREATED: 01/27/09 16:04:01       STATE: active
                       SIZE: 16 MB     ENTRIES: 0
                       FREE PAGES: 4095
# cd /usr/demo/bin
# ls -l hello          # show LLM in UFS
-rwxr-xr-x   1 ROOT    SYSROOT   364544 Feb 20 11:09 hello
# pdbl -u -b hello     # create and save core image
# pdbl -u -l           # show core images in program cache
hello           57 Jan 27 16:05:37 /usr/demo/bin/hello