Get Data Moving 1
Results 1 to 2 of 2

Thread: Mainframe Logging

  1. #1
    Gwyn Jones is offline Attunity Customer Support Consultant
    Join Date
    Sep 2006
    Posts
    28
    Rep Power
    0

    Question Mainframe Logging

    Could you clarify how log files work on a mainframe.

    In my example below, from my PC, there is the opportunity to set a log file in the workspace, serverLogFile, and the binding environment, logFile.

    I believe that in the workspace you can specify %i for the instance but this is not applicable to the binding?

    But this is different on the mainframe. Is there only the SYSOUT spool file to check for the one started task and all its associated subtasks?

    <?xml version="1.0" encoding="UTF-8"?>
    <daemon name="IRPCD">
    <workspaces>
    <workspace name="Navigator" ....
    serverLogFile="NAV_%999i.log"
    </workspace>
    </workspaces>
    <logging logFile="IRPCD.log" />
    <security domainName=""/>
    <versionsPorts/>
    </daemon>

    <?xml version="1.0" encoding="UTF-8"?>
    <binding name="NAV">
    <datasources name="NAV"/>
    <adapters name="NAV"/>
    <environment name="NAV">
    <misc/>
    <debug logFile="nav.log" />
    <queryProcessor/>
    <optimizer/>
    <transactions/>
    <odbc/>
    <oledb/>
    <tuning/>
    <comm/>
    <tempFeatures/>
    </environment>
    </binding>
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

  2. #2
    Join Date
    Sep 2006
    Posts
    233
    Rep Power
    10
    For binding there is no real sense for instance number as there is for a daemon workspace - therefore, the log file in the binding only supports the use of %p which puts in the process ID. This is useful in cases where there are multiple client processes and you want to see the logs of each in a different file. However, this work only on Windows, UNIXes and OpenVMS. For MVS if you use a JCL you can use a DD card to direct the log file name that is provided in the environment definition to any file you want.

    For the servers, only the SYSOUT mechanism is supported. Using log files is not the recommended practice on mainframe for many reasons, one of which is maintainability.
    By Dror Harari

    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •