Not necessarily - if, for example, you have a branch in your VOC LOGIN that varies on usertype or on the login user (eg SYSTEM to avoid having Redback processes run some parts of the LOGIN routine, which is one thing that we do), you might have inadvertantly caused the user id for this process to fail when run by the automated script, but not when run as your user id.

Susan Lynch
F.W. Davison & Company, Inc,
----- Original Message ----- From: <charles_shaf...@ntn-bower.com>
To: "U2 Users List" <u2-users@listserver.u2ug.org>
Cc: "U2 Users List" <u2-users@listserver.u2ug.org>; <u2-users-boun...@listserver.u2ug.org>
Sent: 08/05/2011 11:50 AM
Subject: Re: [U2] Job won't run


Did anything change in your VOC LOGIN program/proc/paragraph that might
be
preventing the program from running?

Susan Lynch
F. W. Davison & Company, Inc.

I don't think so.  Wouldn't that affect the command line run also?

Charles Shaffer
Senior Analyst
NTN-Bower Corporation
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users



_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to