Topic
2 replies Latest Post - ‏2013-03-19T15:31:57Z by SystemAdmin
SystemAdmin
SystemAdmin
47 Posts
ACCEPTED ANSWER

Pinned topic TADz 8.1 - DSNAOCLI module

‏2013-03-18T13:53:56Z |
Hello,
In the TADz 8.1 Beta load library there is a DSNAOCLI module, alias of HSICSQLT. Does the GA version of TADz 8.1 include a DSNAOCLI module? Our TADz 7.5 load library is currently in the linklist ahead of our DB2 load library but when we upgrade to TADz 8.1, if DSNAOCLI is in SHSIMOD1, then other applications looking for DB2's DSNAOCLI will fail with:
HSICSQLT COULD NOT FIND SQLTPATH=path STATEMENT IN DSNAOINI DD
and
ICH420I PROGRAM DSNAOCLI FROM LIBRARY SYS1.SHSIMOD1 CAUSED THE ENVIRONMENT TO BECOME UNCONTROLLED.
BPXP014I ENVIRONMENT MUST BE CONTROLLED FOR DAEMON (BPX.DAEMON) PROCESSING.

Please advise. Thanks.
Updated on 2013-03-19T15:31:57Z at 2013-03-19T15:31:57Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    47 Posts
    ACCEPTED ANSWER

    Re: TADz 8.1 - DSNAOCLI module

    ‏2013-03-19T04:00:51Z  in response to SystemAdmin
    In TADz V8.1, we have defined the DB2 load library ahead of SHISMOD1 in all the STEPLIBs for jobs and procs. This is to support the alias name of HSICSQLT for SQLite. Even if you have SHSIMOD1 ahead of DB2 load library in the linklist, DB2 load library in the STEPLIBs should still take precedence ahead of the linklist. If you have deliberately remove all TADz STEPLIBs, then this will be a problem. Solution would be to place DB2 load library ahead of SHSIMOD1 in the linklist.
    • SystemAdmin
      SystemAdmin
      47 Posts
      ACCEPTED ANSWER

      Re: TADz 8.1 - DSNAOCLI module

      ‏2013-03-19T15:31:57Z  in response to SystemAdmin
      It is not usually deemed an acceptable practice to share module names with another product. DSNAOCLI is a DB2 module and it is expected that it exists only in a DB2 library.

      Does TADz documentation indicate that SHSIMOD1 should not be linklisted?

      As implementors of numerous software packages from multiple vendors, we would greatly appreciate if module names were not shared among different products. Doing so inflicts a level of difficulty to product implementation and maintenance that is simply not necessary.