View Full Version : NT IPC: schedule service doesn't have access to AS/400
01-01-1995, 02:00 AM
I've got a client who has an NT IPCs on their AS/400e running NT Server 4.0 and minimal Client Access. The client has requested an automated job to copy data from the IPC to the AS/400 in order to be included in the AS/400's tape backup. I've written a batch file that copys the data just fine when run manually. However, when the NT Schedule service runs the program, it is unable to attach to the AS/400. It doesn't matter whether I use UNCs, mapped drives, or actually map the drive in the batch file--the result is "Network error 59--an unexpected error has occurred". Am I beating my head against the wrong wall? I'm very new to the AS/400 world, and my AS/400 guru doesn't know anything about Windows NT,PC's, etc. But after three months of failure I'm ready to try anything--perhaps we can get the AS/400 to get the data from the IPC instead of trying to send it?
08-30-2000, 10:59 AM
Use the SAV command to save your QNTC data.
10-24-2000, 08:11 AM
I am having similar difficulties & was looking here for solutions. I have learned a few things which might help you. Suggestions for RUNRMTCMD - Create profile on NT with AS400 compatible name and password (10 char or less, upper case) and a matching profile AS400. Be sure these profiles have necessary authority to objects to be accessed. Go into NT user manager and give this profile authority to run service jobs (see help in Client Access, index, RUNRMTCMD & CWBRXD) Have NT logged on using this user/password --Now you should be able to issue RUNRMTCMD from 400 to this NT box with same user/password which can access IFS objects Suggestions for Schedule service (not "Task Scheduler", update with IE 5.x) Same thing for user profiles Go into Schedule service properties and change "Log On As:" to this user/password -- Now you should be able to schedule jobs on the NT box with AT command which can access IFS objects Hope this helps. Any comments on this are welcome, I am still feel my way though this issue.
Powered by vBulletin® Version 4.1.5 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.