Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Using Decision Stream to Extract As/400 data

Status
Not open for further replies.

donafran

Programmer
Jul 11, 2002
71
US
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

 
If you are using Client Access, I seem to remember there being a dialog box for passing the database ID within it. Try and set this to the required userid and password and see how it goes.
 
We have done that. But it uses the WINDOWS Id and password...if the server is sitting at the "ALT-CTL-DLT to logon" screen, there is no known WINDOWS user id yet...hence our dilemma......if someone physically logs on to the server and does NOTHING else, everything runs fine....but it is the WINDOWS log on (or lack of) that seems to our problem.
Anyone know who to automate the WINDOWS logon on a re-boot ??
 
Check the WinNT forum. I'm sure someone there can help, if it isn't already in a FAQ or an existing thread you can search.

Dave Griffin
The Decision Support Group
Reporting Consulting with Cognos BI Tools
"Magic with Data"
[pc2]
 
IBM Client access has problems connecting via ODBC to the AS400 when intiated from a service (usually SQL server and IIS have this problem). As your system isn't logged in then then it could be a similar problem. The IBM website has some articles on the matter but I've never found a satisfactory solution. The typical answer is to install client access express or to make some changes to the registry of client access. I've tried both of these without success. There must be a workable solution out there though as it's got to be a common occurence!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top