To verify if a file save went through, go to TCL and type:

- T-SELECT and select the correct device for file save

- T-SPACE and it will bring up all accounts that are on the file save

To check if a port is locked:

- Type in LIST-LOCKS in TCL a few times, to verify if any ports are stuck in a lock.

- Then tandem to the port to see the error and then log off the port.

To check CPU usage on a Linux box:

- Go to TCL and type: !TOP which will bring up Linux Usage screen:

PID      USER    PRI  NI  SIZE RSS SHARE STAT % CPU % MEM  TIME CPU COMMAND

14258 mysql     25   0 21736 5860   1680  D       15.1      0.1        84:38    3   mysqld

18234 root        25   0 31520  30M    444   D       14.0      0.6          6:52    3   rar

15555 pick       15    0 66972  65M 66048  S         1.4      1.3          0:25    3   d3

-You will want to look at the PID list in the middle of the screen to see which PID is taking the most CPU% (normally at the top of the list)

- Record the PID number and type Q to exit

- Once back in the TCL, type: ps –ef|grep X(PID number) to find the PIB number

- The PIB will be on first line and will look like:

pick     15555 15554  0 05:04 pts/71   00:00:25 /usr/bin/d3 381

• 381 is PIB number

To restart the PIB if it is not in the list:

!exec d3 –n pick0 (pib) –phantom & <enter>

To kill a PID :

Kill XX(pid#) <enter>

To see what is locking a port:

:where 829

  Ln   PCB   PIB   ABS  Stat  R1 & Return stack contents   08:17:05 19 Apr 2007

       FID   Stat  Base

0829 5EAFD9 BF10 000018  TP4 lk.fail:0ED      lk.ret.lock:072  sv.srch:0F3

                              sv.dump:050

lk fail means it is locked. Now try to find what is locking it:

:list-lockq

  Waiting        owner       fcb    group

line# level   line# level    fid     fid    item id

0051    00                         00D309FE

0121    00                         00D309FE

0339    00                         00B9C9F9

0704    02                         006B9956

0705    01                         006B9956

0709    01                         006B995F

0829    04                         006B9956

The last line above shows us port 829 locking on 006B9956. Now you can find what other port is trying to access 006B9956. The next command below shows us who else is trying to update 006B9956. Note the "Type" Upd means that port is trying to update which causes locks. If the "Type" is Rdo, it is trying to read only which typically will not cause locks.

:list-locks (g

Group Locks         PIB#  Lvl  Type  Filename

11363276 (00AD63CC)   85   1    Rdo    ORDER

11918192 (00B5DB70)   85   1    Rdo    ORDER

7051615 (006B995F)  704   1    Rdo    MASTER

7051615 (006B995F)  705   0    Rdo    MASTER

13830655 (00D309FF)  706   1    Upd    MASTER

7051615 (006B995F)  709   1   -Upd    MASTER

7051606 (006B9956)  709   1    Upd    MASTER

    6379 (000018EB)  829   4    Rdo    mds

6955805 (006A231D)  829   4    Rdo    file-of-files

At this point we are able to determine which port (or ports) we need to logoff.

Another command is CHECK.PIB. See example below:

:check.pib 709

check.pib V1.0                                            08:22:36  19 Apr 2007

pib: 709     Account: PM                Userid: PM               Pid: 1601

-------------------------------------------------------------------Page  1 of  2

BASIC Program Information

Level 1 not running BASIC

Level 0 not running BASIC

Last item referenced

Item   : HA.15E424   or

Item   : A.15E424

Last file: base frame is 2556176

Process type

D3 Process

Phantom Process

RESIZE.ALL (R

Last RTN stack entry points to process in:

Lock processing

-------------------------------------------------------------------------------

(P)rocess, (L)ocks, (S)pooler, (R)unning, (C)ommand, (Q)uit, (A)gain, (M)ain q

Type R for "running" and it will display more information pertaining to that PIB.