Ww:The TDOMS Logging facility
The TD/OMS Logging facility
Normally "errors" are the result of exceptions created by the TD/OMS user. But if something happens during object transfer, we want to know what exactly happened. In the TD/OMS job log you can search for specific error messages generated by TD/OMS. To view the TD/OMS job log, the DSPLOGOMS command is used. You can also use option 13 in the menu "Work management":
OMI004 Log Inquiry 13-10-21
OMI00401 Work with Jobs 15:05:24
------------------------------------------------------------------------------
Application code .......: SBT Sandro Burger Test
Remote address .........: *CURRENT Occurrence date ........: 0-00-00
Filter .................: ____________________________________________________
5=Display 6=Print 8=Display AS/400 job
Date Time Job Fix/Req/Rel
13-10-21 14:57:09 045820/WIM/OM000235 F0472
13-10-21 14:57:09 045820/OMS_ERROR/OM00235 F0472
13-10-21 14:57:03 045818/WIM/QPADEV0003
More...
------------------------------------------------------------------------------
F3=Exit F5=Refresh F12=Cancel
Occurrence date
Enter the date you wish to filter in the list, and the list will display only the jobs started on that date.
Note: By default, jobs from all dates are shown.
Filter
The Filter prompt can be used for quick filtering of the list.
- Filter string
- Type the code or partial code of the fields below that you want to display in the list.
- Job number
- User
- Job name
- Transfer number
- Task (Fix)
Three kinds of log levels are in here: jobs called OMS_ERROR, transfer jobs OM123456 and other jobs. You use option:
- 5 to show the details of the job.
- 6 to create a spoolfile with the details of the job.
- 8 to display the job information. Option 4 of the job information gives you access to the job-specific spoolfiles (e.g. the joblog)
Objects in Error
The OMS_ERROR log provides more information about the specific objects that failed during a transfer. This enables you to pinpoint the cause of the issue.
It states why TD/OMS was having trouble. By using an Error Number.
OMI004 Log Inquiry 13-10-21
OMI00402 Work with Job Messages 15:10:26
------------------------------------------------------------------------------
Application code .......: SBT Sandro Burger Test
Remote address . . . . : *CURRENT Local system
5=Display 8=Display error description
Message Time
_ Start Object Transfer OM000182 for application SBT with Fix F0473, Rel 15:35
_ Warning 15 for object WIMP01, type *PGM to library SBDEV1 from library 15:35
Bottom
------------------------------------------------------------------------------
F3=Exit F5=Refresh F12=Cancel F8=Job F14=Expand F17=Top F18=Bottom
If you place option 8 in front of the line with the error number, you get a detailed description of the cause of the error and how you should react.
For example:
Help 15 - Change Attributes - Help
Number ..............: 15
Severity ............: WARNING
Short description ...: Change Attributes
Reason
You have indicated that OMS should retrieve attributes from the
objects and place them on the newly created objects. This is done in
the application definition function (STRAD.) However, this failed.
Cause
Look at the application definitions and check the attributes
conversion type field. If the value is set to '2=OMSREFOBJ' then
there is not an OMSREFOBJ object in the scope of the transfer. If
the value is set to '1=Adopt' then the object is probably new (first
creation in this environment). OMS is then also looking for the
OMSREFOBJ object.
Recovery
More...
F3=Exit help F10=Move to top F11=Search Index F12=Cancel
Transfer Log
The second one is the general log of transfers.
You can use F14 to collapse/Expand the sections of the transfer. With option 8 we can see the details of a specific section. We can also see if "errors" (in red) or "warnings" (in yellow) occurred. In case of an error, TD/OMS will stop the transfer. In case of a warning, something happened during the transfer, but TD/OMS finished the action anyway.
OMI004 Log Inquiry 13-10-21
OMI00402 Work with Job Messages 15:17:00
-----------------------------------------------------------------------------
Application code .......: SBT Sandro Burger Test
Remote address . . . . : *CURRENT Local system
5=Display 8=Display Section
Message Time
_ Start Object Transfer OM000222 for application SBT with Fix F0472, Rel 18:40
_ Start library list 00010 in environment *DEV 18:40
_ Action 'Constraints process, FROL file unaffected' in step SL compl 18:40
_ Action 'Triggers process, FROL file unaffected' in step SL complete 18:40
_ Start creating member MCPSRVPGM of object SBDEVDTL/QCPYLESRC type *FIL 18:40
_ Library OM000222 created. 18:40
_ Authority changed for OM000222/OMFBC type *FILE 18:40
_ Start creating member MCPSRVPGM2 of object SBDEVDTL/QCPYLESRC type *FI 18:40
_ Detail MCPSRVPGM2 in object SBDEVDTL/QCPYLESRC is assumed to be cop 18:40
_ Start creating object SBDEV/ABCDEF1 type *PGM. 18:40
More...
-----------------------------------------------------------------------------
F3=Exit F5=Refresh F12=Cancel F8=Job F14=Expand F17=Top F18=Bottom
"Start rebuilding relations" is the last line in the job log of every transfer.
If TD/OMS "dumps" a program, a spool file is created containing information about the reason for the dump.
Log Analysis
All log entries are stored in file OMLOG. With this file, you can do a log analysis. Here are some of the messages that you could query for:
Message ID Severity Message Text
OTP0031 0 Start creating object &5/&3 type &4.
OTP0032 0 Start creating &9 &7 of object &5/&3 type &4.
OTP0033 0 Start deleting object &5/&3 type &4.
OTP0034 0 Start deleting &9 &7 of object &5/&3 type &4.
OTP1003 0 Start creating &1 object &3.
OTP1004 0 Start deleting &1 object &3.
Below is an example of what you could see in the log.
5=Display 8=Display Section
Message
OTP0001 Start Object Transfer OM008315 for application XMP with Fix XT0210
OTP0002 Start library list 00161 in environment *TST
OTP0034 Start deleting member MCPSRVPGM of object SBDEVDTL/QCPYLESRC type *FILE.
OTP0032 Start creating member MCPSRVPGM2 of object SBDEVDTL/QCPYLESRC type *FILE.
OTP0034 Start deleting message ID MSG0002 of object SBDEV/SBTSTMSG type *MSGF.
OTP0032 Start creating message ID MSG0005 of object SBDEV/SBTSTMSG type *MSGF.
OTP0033 Start deleting object SBDEV/ABCDEF1 type *PGM.
OTP0031 Start creating object SBDEV/ABCTST4 type *PGM.
OTP1003 Start creating *STMF object add.phtml.
OTP1004 Start deleting *STMF object application.ini.
OTP0013 Starting clean-up
OTP0012 Starting distribution.
OTP0009 Processing completed normally. 7 object(s) created.
OTP0007 Processing ended with 1 errors and 0 warnings