WebSphere App Server CL start/stop script for System i

WebSphere App Server on the i/OS does not come with a feature to automatically start and stop, and sometimes its best to use a CL command to stop it. I frequently see users doing an ENDSBS(WAS7), which wreaks havoc with the JVM. Please don't just end the subsystem. When you do this, the JVM drops all logging and can leave some config files corrupted.  This then requires extra clean up time when the system is restarted, which can cause your CPU to work overtime.

There is a script in the InfoCenter, but after a recent call with support, we decided to use one that utilizes QSHELL rather than SBMJOB technique outlined in the InfoCenter.

WAS CL Startup Script

    100 PGM                        
    200              CHGJOB     LOG(4 00 *SECLVL) LOGCLPGM(*YES)             
    300              STRSBS     SBSD(QWAS7/QWAS7)                            
    400              MONMSG CPF0000
    500              DLYJOB     DLY(30)                                      
    600                            
    700              QSH        +  
    800                           CMD('/qibm/userdata/websphere/appserver/v7/+
    900                           nd/profiles/dmgr01/bin/startServer')       
   1000              DLYJOB     DLY(30)                                      
   1100                            
   1200              QSH        +  
   1300                           CMD('/qibm/userdata/websphere/appserver/v7/+
   1400                           nd/profiles/hats/bin/startServer nodeagent')
   1500              DLYJOB     DLY(30)                                      
   1600                            
   1700              QSH        +  
   1800                           CMD('/qibm/userdata/websphere/appserver/v7/+
   1900                           nd/profiles/hats/bin/startServer HATS9081')
   2000              DLYJOB     DLY(30)                                      
   2100                            
   2200              QSH        +  
   2300                           CMD('/qibm/userdata/websphere/appserver/v7/+
   2400                           nd/profiles/hats/bin/startServer HATS9082')
   2500              DLYJOB     DLY(30)                                      
   2600                            
   2700              QSH        +  
   2800                           CMD('/qibm/userdata/websphere/appserver/v7/+
   2900                           nd/profiles/hats/bin/startServer HATS9083')
                                  * * * *  E N D  O F  S O U R C E  * * * *

WAS CL Shutdown Script

100 PGM
200 CHGJOB LOG(4 00 *SECLVL) LOGCLPGM(*YES)
300 QSH +
400 CMD('/qibm/userdata/websphere/appserver/v7/+
500 nd/profiles/hats/bin/stopServer HATS9081')
600 DLYJOB DLY(30)
700
800 QSH +
900 CMD('/qibm/userdata/websphere/appserver/v7/+
1000 nd/profiles/hats/bin/stopServer HATS9082')
1100 DLYJOB DLY(30)
1200
1300 QSH +
1400 CMD('/qibm/userdata/websphere/appserver/v7/+
1500 nd/profiles/hats/bin/stopServer HATS9083')
1600 DLYJOB DLY(30)
1700
1800 QSH +
1900 CMD('/qibm/userdata/websphere/appserver/v7/+
2000 nd/profiles/hats/bin/stopServer nodeagent')
2100 DLYJOB DLY(30)
2200
2300 QSH +
2400 CMD('/qibm/userdata/websphere/appserver/v7/+
2500 nd/profiles/dmgr01/bin/stopServer')
2600 DLYJOB DLY(30)
2700
2800 ENDSBS SBS(QWAS7) OPTION(*CNTRLD) DELAY(30)
2900 monmsg cpf0000
* * * * E N D O F S O U R C E * * * *

Note that above there is a delay job. This is set at 30 seconds, but 5 minutes is more appropriate depending upon the speed of your system and workload being performed.

10 reasons to patch your Lotus Domino 8.5.1 Server to Fix Pack 3

Lotus Domino and Notes fix pack 3 for 8.5.1 was released 3 days ago and already you should be considering patching your environment for these 10 reasons. Here are 8 fixes that apply to the server, followed by two that apply to the clients that you should not miss out on. The server fix pack only takes about 20 minutes maximum to apply. You can roll out your client fixes via SmartUpgrade.  The client fixes are in my opinion not as high of a priority as the server fixes listed below. If your clients are experiencing the two issues I've highlighted you could roll those out using Domino explicit policies.

Domino 8.5.1 fix pack 3 server fixes

SPR# ADEE84REF5

Fixed a defect that affects attachments during archive operations, causing attachment corruption. This regression was introduced in 8.5.1

SPR# CAOA83W73Y

Fix for two memory leaks in the backend classes exposed by customer using xpages.

SPR# CSCT836HFL

View.getDocumentByKey and getAllDocumentsByKey fails on a very busy View, with a "the collection has become invalid" error. This fix will allow collection retrieval under all commonly occurring conditions and is primarily for the server, but will pertain to both client and server. This regression was introduced in 8.5.1. (Technote #1424178)

SPR# DADS7VJRSQ

When registering users via the admin client and adding the new user to groups, the registration server will crash. With this fix applied to the registration server, the admin client will successfully register the user without the registration server crashing. (Technote #1428766)

SPR# KLYH7ZPNC2

Fixed IBM Lotus Domino LDAP buffer overflow vulnerability. (Technote #1420749). If your Domino server sits open to the Internet - THIS IS A MUST APPLY FIX! Do not dance around with security vulnerabilities.

SPR# WBKK7GNJY8

Fix for Cluster Replicator crash which could happen under low memory conditions. (Technote #1314039)

SPR# JSHN7YSRPZ

Fixed a problem where the Out of Office Service was responding to an incorrect address. The Out of Office Service was enabled for a user and they responded to a message from a sender in a different Notes domain. The user then received a message from another sender in the same Notes domain as the user. When that second message was responded to, the Notes domain of the first sender was appended to the address, which resulted in an invalid address and ultimately a delivery failure. (Technote #1431077)

SPR# OIHZ7R3KFK

With a Notes 8.0.2 server set to use the Out of Office Service and after upgrading to 8.5, some users are using the Out of Office agent instead of the service. This occurs for all users who have the Out of Office service enabled at the time of the load convert to the new mail template. This regression was introduced in 8.5.1. (Technote #1425342)

Lotus Notes 8.5.1 fix pack 3 client fixes

SPR# MHUZ7W5LDD

When the desktop policy "Enable 'Synchronize Contacts' on the replicator" is enabled, the setting is not honored well on replication page. This fix will make the setting honored well on the replication page.

SPR# JPAI82QP5S

Fixed a regression which prevents Smart Upgrade from successfully launching a .bat or .cmd file. The workaround would be to launch "cmd.exe" and put the .bat or .cmd file in the Optional Arguments in the Smart Upgrade Kit. This regression was introduced in 8.0.2.

The full list of fixes is available on the Notes/Domino fix list site, where you can peruse all the fixes, not just the ones I've highlighted.