Routing Operator Messages in WebSphere Application Servers for z/os V6 & V7

Transcription

1 Routing Operator Messages in WebSphere Application Servers for z/os V6 & V7 Operator informational and error messages are normally directed to JES Spool datasets. Examples of these include: RAS Traces & output from System.out.println are directed to the SYSPRINT DD file. Error log output, output from System.err.println, and verbose GC directed to SYSOUT Errors caught by LE or the Java run-time are written to the CEEDUMP file. Here is a sample of the output DD statements in the included &Z members for the WebSphere started task procedures as distributed from IBM: SYSOUT=* means to send it to the JES SYSOUT class for the started task, which is usually a held class, so it is not normally printed. SPIN=UNALLOC prevents JES from discarding these data sets in the event of a restart by the automatic restart manager (ARM). Note: In WebSphere Application Server for z/os V7, the following DD statements are included in the PROCLIB members provided by the configuration scripts: //DEFALTDD DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE //HRDCPYDD DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE Enhanced Message Routing Capabilities: WebSphere Application Server for z/os provides several improved message routing capabilities: 1. Route BBO messages to specific datasets instead of SYSLOG, to relieve the clutter on SYSLOG. 2. Spin off SYSOUT and SYSPRINT data sets to relieve spool resources. 3. Route these datasets to HFS files instead of to JES Spool so they can be viewed by personnel more familiar with UNIX than with TSO. 1. Routing BBO Messages away from Joblog (Cleaning up SYSLOG) You can route many of the BBO prefixed error messages to specific datasets instead of having TD Routing Operator Messages in WebSphere for z/os Servers Page 1 of 6

2 them go to the SYSLOG, which can create a lot of traffic. This is implemented with the use of two new environment variables. To use these message routing variables, add these parameters to the server definitions using the Administrative Console under Environment -> Manage WebSphere Variables: ras_default_msg_dd = DEFALTDD ras_hardcopy_msg_dd = HRDCPYDD You can set these variables for individual control and servant processes, but it is easier to set them in the Environment variables for the entire cell. For the Daemon, you must prefix them with "DAEMON_" and set them at the cell level: DAEMON_ras_default_msg_dd =DEFALTDD DAEMON_ras_hardcopy_msg_dd =HRDCPYDD Note: This updated document contains a jython script to set these variables: ras_default_msg_dd=defaltdd ras_hardcopy_msg_dd=hrdcpydd ras_time_local=1 DAEMON_ras_default_msg_dd=DEFALTDD DAEMON_ras_hardcopy_msg_dd=HRDCPYDD DAEMON_ras_time_local=1 Then update the included &Z members in PROCLIB to add these new DD statements: //DEFALTDD DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE //HRDCPYDD DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE WAS Version 7 Note: There are no &Z members, and these DD statements (DEFALTDD and HRDCPYDD) are already included in the PROCLIB members provided by the configuration scripts in WebSphere Application Server for z/os V7. For more details, see the article on Managing operator message routing in the WebSphere for z/os InfoCenter at:: Using the supplied jython script to initialize these variables There us a jython script supplied with this techdoc initsetvarsv7.py that you can use to initialize the ras message DD variables. TheupdNewServer.py script assumes the WSC cell naming convention (see techdoc WP ) If some other naming convention is in use, then minor TD Routing Operator Messages in WebSphere for z/os Servers Page 2 of 6

3 modification of the provided script would be required. The invocation of the script for this particular example might look like this (all on one line without the back-slash \ ):./wsadmin.sh lang jython javaoption - \ Dscript.encoding=IBM f scriptpath/initsetvarsv7.py The output of the script, which would look as follows: WASX7209I: Connected to process "dmgr" on node h7dmnode using SOAP connector; The type of process is: DeploymentManager Cell variable is (cells/h7cell Adding the following variables and values to the cell h7cell scope: DAEMON_ras_default_msg_dd=DEFALTDD DAEMON_ras_hardcopy_msg_dd=HRDCPYDD ras_default_msg_dd=defaltdd ras_hardcopy_msg_dd=hrdcpydd ras_time_local=1 DAEMON_ras_time_local=1 TZ= EST5EDT Skipping node h7dmnode Skipping node h7nodea 2. Spinning off SYSOUT and SYSPRINT data sets: Output files are not released from JES spool until the server address spaces are re-cycled and can build up over time, causing a large demand on spool space if there are a lot of messages are being written. In a JES2 system, this problem can be relieved by segmenting portions of the spool files, so they can be dynamically spun off. Once the segments are printed, offloaded, or purged, the spool space is unallocated and freed. However, segmentation is only supported for output files which have page boundaries (formfeed characters). Support is provided to periodically write form-feed characters so the output can be segmented. Two new custom properties for the application servers were introduced to specify the time in minutes) between writing form-feed characters: ras_stdout_ff_interval for standard output (SYSPRINT). ras_stderr_ff_interval for standard error (SYSOUT). Once the page-count threshold for segmentation is reached, JES2 will spin off those pages, so they can be held, printed, re-routed, or purged. The page-count is specified by the SEGMENT parameter on the DD JCL statement. To set these custom properties using the administrative console (ISC): Click Application servers > server_name> Server infrastructure > Administration > Custom Properties. To specify this for a deployment manager, click System administration > Deployment manager, then under Server Infrastructure, click > Java and Process Management > Process Definition > Java Virtual Machine > Custom Properties. You can also go to: Environment > WebSphere Variables, and add them at the cell, node, or server scope as you desire. TD Routing Operator Messages in WebSphere for z/os Servers Page 3 of 6

4 Choosing the form-feed Interval and Segment size: Decide how often you want to spin the output and how you want to break it up into pages. The product of the values for ras_stdxxx_ff_interval and the SEGMENT parameter determines how frequently the output will be spun off. For example, to spin the output once a day (every 1440 minutes) specify: form-feed every twelve hours (720 minutes) and SEGMENT=2, or form-feed every hour (60 minutes) and SEGMENT=24... or to spin them once a week (every minutes) specify: form-feed every day (1440 minutes) & SEGMENT=7, or form-feed every hour (60 minutes) and SEGMENT=168 Usage Considerations: Once you hit the limit defined by JES2 OUTDEF SEGLIM initialization parameter, JES2 won t spin any more output until the address space terminates. SEGLIM=1 prohibits SYSOUT segmentation. SEGLIM=99999 allows practically unlimited SYSOUT segmentation. The default value is SEGLIM=100 Since the default value is likely to be set to 100 on your system, you probably want to use a less frequent form-feed, and smaller SEGMENT size such as ff_interval=360 (6 hours), and SEGMENT=4 to spin every day. Another consideration, is the number of different output groups that may be created; excessive output groups may be limited by the JES2 OUTDEF NUMJOES initialization parameter, and create problems in managing all the segments. Many of these output groups will have no data records if you are not tracing or writing messages to spool, so don t implement this segmentation unless you have a need. SYSPRINT Example: Here is an example to spin SYSPRINT every day: Set ras_stdout_ff_interval=360 in the custom properties of your application server Update the INCLUDE members in Proclib for the controller, servant, and adjunct procedures to specify SEGMENT=4 on the //SYSPRINT DD: //CEEMSG DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE,SEGMENT=4 SYSOUT example: This must be handled differently because of the way that WAS redirects stderr from the LE environment. You have two choices, either: 1. Redirect the Java stderr to a new DD such as SYSERR, or 2. Direct the LE runtime stderr to a new DD such as CEEMSG, and Java stderr to SYSOUT. TD Routing Operator Messages in WebSphere for z/os Servers Page 4 of 6

5 The recommended way is (1) to redirect java stderr to a new DD card. 1. Redirecting Java stderr to SYSERR and spinning every week: Update the members in Proclib for the controller procedure to specify the additional parm to redirect Java stderr to SYSERR. Pay attention to JCL continuation card rules for parameters within quotes: To continue a parameter enclosed in quotes, extend it to a comma, or to column 71. Code // in columns 1 and 2 of the following statement, and continue the parameter in column 16 of the following statement. (If following a comma, the next parameter can start anywhere between columns 4 and 16.) Parameter arguments passed to LE Environment are before the slash (/); arguments for the execution program are placed afterwards. Here s how you might code the parameters for a controller region procedure: //BBOCTL EXEC PGM=BBOCTL,COND=(4,LT,APPLY),REGION=0M,TIME=MAXIMUM, X // PARM='TRAP(ON,NOSPIE),ENVAR("_EDC_UMASK_DFLT=007") /X // &PARMS. REC=&REC 2>DD:SYSERR' Here s how you might code the parameters for a servant or adjunct region procedure: //BBOSR EXEC PGM=BBOSR,REGION=0M,TIME=NOLIMIT, // PARM='TRAP(ON,NOSPIE),ENVAR("_EDC_UMASK_DFLT=007") /2>DD:SYSERR' Setras_stderr_ff_interval=1440 in the custom properties. Update the INCLUDE members in Proclib for the controller, servant, and adjunct procedures to add a //SYSERR DD statement, just like the current //SYSOUT statement, and specify SEGMENT=7 on the //SYSERR DD statement: //SYSERR DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE,SEGMENT=7 2. Redirecting CEE stderr to CEEMSG and spinning SYSOUT every week: Update the members in Proclib to specify the additional parms to redirect LE stderr to CEEMSG, and Java stderr to SYSOUT. Note that the LE parameter MSGFILE(CEEMSG) is before the slash (/), and the redirection of stderr 2>SYSOUT is afterwards. Here s how you might do it for the controller s procedure: //BBOCTL EXEC PGM=BBOCTL,COND=(4,LT,APPLY),REGION=0M,TIME=MAXIMUM, X // PARM='TRAP(ON,NOSPIE),ENVAR("_EDC_UMASK_DFLT=007"),MSGFILE(CEEMSG) /X // &PARMS. REC=&REC 2>DD:SYSOUT' Here s how you might code the parameters for a servant or adjunct region procedure: TD Routing Operator Messages in WebSphere for z/os Servers Page 5 of 6

6 //BBOCTL EXEC PGM=BBOCTL,COND=(4,LT,APPLY),REGION=0M,TIME=MAXIMUM, X // PARM='TRAP(ON,NOSPIE),ENVAR("_EDC_UMASK_DFLT=007"),MSGFILE(CEEMSG) /X // 2>DD:SYSOUT' Setras_stderr_ff_interval=1440 in the custom properties. Update the INCLUDE members in Proclib for the controller, servant, and adjunct procedures to add a //CEEMSG DD statement with the same parameters as the original //SYSOUT DD STATEMENT, and add SEGMENT=7 to the //SYSOUT DD statement: //CEEMSG DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE,SEGMENT=7 Purging spun-off output files Once output has been spun off, you can display the individual pieces of output using C (cancel command on the SDSF H (held) or O (output) panel. SDSF HELD OUTPUT DISPLAY NP JOBNAME JobID O-Grp-N OGID1 OGID2 C CGAGNTA STC CGAGNTA STC CGLRSAS STC This results in the following JES2 command: $COS(537),OUTGRP=8.1.1 To display the output groups for a particular started task, such as STC00537, issue this JES2 command: $DOS(537),LONG 3. Routing output to an HFS file instead of to JES SPOOL You can also direct SYSPRINT, SYSOUT, and other files described above to an HFS. The sample JCL below shows how to modify the SYSPRINT DD card in your startup procedure to redirect the output to an HFS file in the "/mydir/myserver" directory, in this case, named was.log.d&lyymmdd..t&lhhmmss //*YSPRINT DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE //SYSPRINT DD PATHMODE=(SIRWXU,SIRWXG,SIROTH), // PATHOPTS=(OWRONLY,OCREAT), // PATH='/myDir/myServer/was.log.d&LYYMMDD..t&LHHMMSS' Note: You cannot route these output messages to BOTH JES SPOOL and an HFS file; you must pick one or the other. For more details, see SYSPRINT output, STDOUT and STDERR streams in an HFS File in the WebSphere for z/os InfoCenter at TD Routing Operator Messages in WebSphere for z/os Servers Page 6 of 6