I found this question on a message forum, wrote a note, and forgot about it:
Anyone have any tricks on suspending the process schedulers programmatically? I just tried using the following but the weird thing was I saw at least one of my process schedulers unsuspend itself, so I must be missing an update to a table.
UPDATE PSSERVERSTAT set SERVERSTATUS = '2' where SERVERNAME like '%PSUNX%'
The process scheduler writes its status to SERVERSTATUS so that it can be seen in the Process Monitor. Instructions to the process scheduler are read from SERVERACTION, so this is the column that must be updated. Both columns have a set of XLAT values that translate the status.
PeopleSoft Field Name | Description |
---|---|
SERVERSTATUS | Server Status 0=Error 1=Down 2=Suspended 3=Running 4=Purging 5=Running With No Report Node 6=Suspended - Disk Low 7=Suspended - Offline 8=Running - Report Rep. Full 9=Overloaded |
SERVERACTION | Process Server Action 0=None 1=Stop 2=Suspended 3=Restart 4=Purge |
- Stop
update psserverstat
set serveraction = 1 /*Stop*/
where serverstatus = 3 /*Running*/
and servername = …
/
commit
/
- Suspend
update psserverstat
set serveraction = 2 /*Suspend*/
where serverstatus = 3 /*Running*/
and servername = …
/
commit
/
- Restart (after suspension)
update psserverstat
set serveraction = 3 /*Restart*/
where serverstatus = 2 /*Suspended*/
and servername = …
/
commit
/
- Startup (if the Tuxedo domain is running)
update psserverstat
set serveraction = 3
where servername = …
/
commit
/
No comments :
Post a Comment