1. Problem: Can t see Messages in Message Monitor Possible Causes: I. Channel Security not set. II.

Message Monitor view criteria is too limiting (looking at the wrong time, ch annel, node, etc.) Actions: Take corrective measures. 2. Problem: My Publish() PeopleCode finishes successfully, but there is no messa ge in the Message Monitor. Possible Causes: I. The Message Definition is InActive. Actions: Take corrective measures. 3. Problem: Message Instance sits in NEW status. Possible Causes: 1. Application Server down. II. Pub/Sub services not configured on Application Server domain. III. Message Broker Dispatcher down. Actions: Check pub/sub services and reboot them if necessary. 4. Problem: Message Instance sits in WORKING status. Possible Causes: I. Message Broker Handler crashed. Actions: Take corrective measures. Resolution of Messages with Error status 1. From Sub Contracts Page, click on details for message in Error status. 2. Next, click on the Message Errors tab and check the Error Message 3. If the Error Message does not imply a solution then check on the app server l og file for error message details, at /ps/c1prd/appserv/C1PRD/LOGS/APPSRV.LOG For example: PSSUBHND_dflt.1169 [08/15/01 08:00:14 SubConProcess](1) GenMessageBox(6540, 11, M): Component Processor: Warning -- Address should consist of at least Street an d City. (6540,11) PSSUBHND_dflt.1169 [08/15/01 08:01:25 SubConProcess](1) GenMessageBox(200, 0, M) : /ds3/home/build81/pt81410rc6-retailr_o/src/psppr/ramget.cpp: SQL error. Stmt # : 609 Error Position: 0 Return: 8118 - Memory allocation failed (SQLSTATE PS11 8) PSSUBHND_dflt.1169 [08/15/01 08:01:25 SubConProcess](1) GenMessageBox(200, 0, M) : SQL Access Manager: SELECT COUNTRY, DESCR, ADDR1_LBL, ADDR1_AVAIL, ADDR2_LBL, ADDR3_LBL, ADDR4_LBL, CITY_LBL, CITY_AVAIL, NUM1_LBL, NUM2_LBL, HOUSE_TYPE_LBL, ADDR_FIELD1_LBL, ADDR_FIELD2_LBL, ADDR_FIELD3_LBL, COUNTY_LBL, STATE_LBL, POSTAL _LBL, POST_SRCH_AVAIL, GBSYS_NRPATH_UK, GBSYS_CFGPATH_UK FROM PS_COUNTRY_TBL WHE RE COUNTRY=:1 ORDER BY COUNTRY PSSUBHND_dflt.1169 [08/15/01 08:01:25 SubConProcess](1) GenMessageBox(200, 0, M) : /ds3/home/build81/pt81410rc6-retailr_o/src/psapmsg/logerror.cpp: SQL error. St mt #: 628 Error Position: 0 Return: 8118 - Memory allocation failed (SQLSTATE PS118) PSSUBHND_dflt.1169 [08/15/01 08:01:25 SubConProcess](1) GenMessageBox(200, 0, M) : SQL Access Manager: SELECT MAX(SEQNO) FROM PSAPMSGSUBCERR WHERE PUBNODE = :1 A ND CHNLNAME = :2 AND PUBID = :3 AND MSGNAME = :4 AND SUBNAME = :5 4. In this case, we resubmitted the message (see step#1 for Resubmit button) and it later successfully processed. SQL and PC Trace options for App Server - good for checking if SQL events didn't take place or if Subscription PC didn't fire properly. SQL Tracing on App Serv :In the AppServer Configuration file you can set the tra

ce options. Trace After you have set the Domain Settings the Trace section appears. This section a llows you to specify the tracing options that you can enable on the application server to track the SQL and PeopleCode of your domain(s). Values for config section - Trace TraceSql=0 TraceSqlMask=12319 TracePC=0 TracePCMask=4095 TracePPR=0 TracePPRMask=4095 TraceAE=0 Write crash dump to separate file=Y Do you want to change any values (y/n)? [n]: TraceSQL Sets logging level for SQL tracing for all clients. Traces are written to the fo llowing location: <PS_HOME>/appserv/<domain>/LOGS/<DomainOPRID>_<svrname>.traces ql. If you enter 0 it disables tracing; use 7 to enable a modest tracing level for d ebugging. For other levels of tracing, set to a value equal to the sum of the de sired options. For example, if you only want to trace SQL, TraceSQL=1; if SQL st atements and Connect statements are desired, TraceSQL should be set to 1+ 2 + 4 = 7. A setting of TraceSQL = 7 is recommended for troubleshooting connection and other basic problems. Tracing can consume large amounts of disk space over time so be sure to reset TraceSQL = 0 when you've finished trouble shooting. TraceSQLMask Sets logging level ceiling for SQL tracing for individual clients. Traces are wr itten to the following location: <PS_HOME>/appserv/<domain>/LOGS/<ClientOPRID>_< svrname>.tracesql. Clients must specify desired SQL tracing level using PeopleSo ft Configuration Manager on the Trace tab. To prevent clients from turning on th e application server trace, and consuming resources, the application server uses TraceSQLMask as an administrative control facility. If a client transmits a request to trace SQL, the application server compares th e value transmitted to TraceSQLMask. If the client value is less than or equal t o TraceSQLMask, the application server enables the trace. However, if the client value is greater, application server will enable the trace up to the TraceSQLMa sk value. Trace files are written on the application server; no trace shows up o n the client workstation. Trace values are set in the application server configuration file psappsrv.cfg f ile. Output files are written to directory $PS_HOME/appserver/winx86/<domain>/lo gs. For TraceSQL and TraceSQLMask you have the following options: 1 - SQL statements 2 - SQL statement variables 4 - SQL connect, disconnect, commit and rollback 8 - Row Fetch (indicates that it occurred, not data) 16 - All other API calls except ssb 32 - Set Select Buffers (identifies the attributes of columns to be selected). 64 - Database API specific calls 128 - COBOL statement timings

256 512 4096 8192 TracePC

Sybase Bind information Sybase Fetch information Manager information Message Agent information

Sets a desired level for PeopleCode tracing for activity generated by all client s on a domain. Eligible values will be defined in the configuration file. TraceP C values are displayed in the Configuration Manager on the Trace tab. You can fi nd the results in the following location: <PS_HOME>/appserv/<domain>/LOGS/<domai n>.log. TracePCMask This parameter controls which of the PeopleCode Trace options requested by clien t machines will be written to the trace file. The results of this trace are writ ten to <PS_HOME>/appserv/<domain>/LOGS/<ClientMachine>.<domain>.log For TracePC and TracePCMask you have the following options. 1 - Trace instructions 2 - List the program 4 - Show assignments to variables 8 - Show fetched values 16 - Show stack 64 - Trace start of programs 128 - Trace external function calls 256 - Trace internal function calls 512 - Show parameter values 1024 - Show function return value 2048 - Trace each statement in program For the TraceSQL I would like for you to use a value of "5" and for the TracePC use a value of "10"