What are some debugging techniques?
Each IH subsystem maintains a log with the name ‘trnpre.ihubssid.REGION.LOG’ which can be browsed from ISPF. The IH option LOG CLOSE must be set to insure the log messages are not buffered. When the REGION.LOG is full (i.e. out of extents or DASD space), IH sends a message to the MVS console and stops logging. Also, there is an optional log for each schema with the name ‘prefix.schema.LOG’ which can be browsed from ISPF. By default schema logging is off. From the mainframe, IH updates the schema log if LOGGING ON is specified when entering the TSO INFOHUBM or CICS IHUB command. From the client, IH updates the schema log if the the ODBC check box LOGGING is checked. It’s may also useful to check the box DBTRAP. Note that some front end applications like Powerbuilder or MS-Access may open multiple connections. In this case schema logging must not be turned on. The first connection will cause IH to issue an MVS open for update on the schema.log file. The second connection will also try to
