We currently have the Version 6.0, 6.6 versions of all the Cognos software components.
We run our daily Decision Stream process to extract transaction data from an As/400 into the Cognos datamart (MS SQL database on WIN NT). This is done via a batch job on the AS/400 using RUNRMT command to execute the .bat or .cmd file that contains the Decision Stream commands on the NT Server and normally runs fine.
We have, over the last 18 months, come to the conclusion that the NT Server environment is much more stable if it is rebooted periodically. We have automated the re-boot for over the weekend. (less Dr. Watson and Memory Errors)
Problem: when the server is sitting at the "Hit Alt-CLT-Dlt to log-on" screen, it seems that the AS/400 Connection is not 100% functional.
I can use the RUNRMT command from the As/400 and successfully run other .cmd/.bat files on the NT server that use Impromptu and other applications on the NT Server,that access data already residing on the NT server. But when I try to run the Decision Stream job, which uses the ODBC connection to the As/400, the job starts, but then hangs less than one minute into processing.
Bottom line: The RUNRMT from the As/400 seems to find the NT Server and kick off the job. When Decision Stream needs the ODBC connection back to the AS/400, the job hangs. Any one have any advice ?? These are jobs that run 3:00am-7:00am !!
If I actually log onto the server and re-run the job, it runs PERFECTLY !!
It has to be a connection between the log-on screen and the AS/400 ODBC connection.
Thanks
We run our daily Decision Stream process to extract transaction data from an As/400 into the Cognos datamart (MS SQL database on WIN NT). This is done via a batch job on the AS/400 using RUNRMT command to execute the .bat or .cmd file that contains the Decision Stream commands on the NT Server and normally runs fine.
We have, over the last 18 months, come to the conclusion that the NT Server environment is much more stable if it is rebooted periodically. We have automated the re-boot for over the weekend. (less Dr. Watson and Memory Errors)
Problem: when the server is sitting at the "Hit Alt-CLT-Dlt to log-on" screen, it seems that the AS/400 Connection is not 100% functional.
I can use the RUNRMT command from the As/400 and successfully run other .cmd/.bat files on the NT server that use Impromptu and other applications on the NT Server,that access data already residing on the NT server. But when I try to run the Decision Stream job, which uses the ODBC connection to the As/400, the job starts, but then hangs less than one minute into processing.
Bottom line: The RUNRMT from the As/400 seems to find the NT Server and kick off the job. When Decision Stream needs the ODBC connection back to the AS/400, the job hangs. Any one have any advice ?? These are jobs that run 3:00am-7:00am !!
If I actually log onto the server and re-run the job, it runs PERFECTLY !!
It has to be a connection between the log-on screen and the AS/400 ODBC connection.
Thanks