Does anyone have any simple step-by-step instructions for doing MIMS tracing?
I'm trying to put together a simple document that even a newbie system administrator can follow. I don't want to reinvent the wheel if someone has already done it.
The Mincom instructions aren't very helpful, as they seem aimed more at explaining the theory of tracing rather than a simple "HOW-TO" document.
I also have an intermittent problem using DEBUG servers. Sometimes they work great, other times I get a "Communication Error".
Here's the documentation I've started:
There are four types of traces.
1. On-data,
2. On-line,
3. Batch &
4. Front end.
In addition Mincom may request screen dumps or a Screen Cam. We don’t have screen cam, we use SnagIt instead.
For On-data, On-line and Batch traces you first need to compile the program with trace.
You may also need to re-compile some subroutines with trace.
You may need to bounce the application servers
Empty out any existing trace files:
(Only required for ONDATA trace, where user1 is the user's MIMS logon-id)
For ONDATA trace
Check the trace box on the login window. <<screen dump>>
For FRONT-END trace
Right click the MIMS icon in the task bar, and choose Properties
UI Connectivity: Set both to Medium <<screen dump>>
UI Debug: <<screen dump>>
I'm trying to put together a simple document that even a newbie system administrator can follow. I don't want to reinvent the wheel if someone has already done it.
The Mincom instructions aren't very helpful, as they seem aimed more at explaining the theory of tracing rather than a simple "HOW-TO" document.
I also have an intermittent problem using DEBUG servers. Sometimes they work great, other times I get a "Communication Error".
Here's the documentation I've started:
There are four types of traces.
1. On-data,
2. On-line,
3. Batch &
4. Front end.
In addition Mincom may request screen dumps or a Screen Cam. We don’t have screen cam, we use SnagIt instead.
For On-data, On-line and Batch traces you first need to compile the program with trace.
Code:
mscomp -t3 msx999
You may also need to re-compile some subroutines with trace.
Code:
mscomp -t3 mss999
You may need to bounce the application servers
Code:
mschklop
tp_op -Kw 99999
Empty out any existing trace files:
Code:
cd trace
ls -l
>user.trc # Redirect nothing to user.trc
/app/mims_dev/mims43d/mims_run/trace/» mstrace
Enter client username for tracing (mims43d)...:user1
Code:
Client Username is user1...
Enter trace file to be generated (user1.trc).:
Enter log file to be generated (user1.log).:
Enter server type to be traced:
Valid server types are online, batch, ondata (online).:ondata
ondata server started. To attach to this server select the Debug box on the client login window.
(/bin/ksh) mims43d@seven MIMS43D
/app/mims_dev/mims43d/mims_run/trace/»
For ONLINE trace (Terminal or SmartGUI)
Type &TRACEON at MSO000
07/03/01 DEV * DEV * DEV * DEV * @seven MSM000B.014A
10:59:36 GENERAL MENU 4.3.12.016E
GM
1. MAINTMNU MAINTENANCE OPERATIONS
2. PURCHASE PURCHASING
3. CATALOGUE CATALOGUE MAINTENANCE
4. SUPPLIERS SUPPLIER MAINTENANCE
5. WAREHOUSE WAREHOUSE OPERATIONS
6. ACCOUNTSRE ACCOUNTS RECEIVABLE
7. OPERATIONS PLANT OPERATIONS
8. ENQUIRIES GENERAL ENQUIRIES
----------------------------
9. MSO022 CHANGE PASSWORD (AT ANY TIME)
ENTER Option &TRACEON
OR Userid and Password
F5-Welcome Scr, F7-Diary Msg, F8-Chg Dstrct
TRACE ON
For ONDATA trace
Check the trace box on the login window. <<screen dump>>
For FRONT-END trace
Right click the MIMS icon in the task bar, and choose Properties
UI Connectivity: Set both to Medium <<screen dump>>
UI Debug: <<screen dump>>