I am using VC 7.04 with several jobs that monitor file creation in a folder on an Iseries to trigger a task.
Whenever I try to enable the trigger it immediately disables the trigger with an access denied. I have credentials defined, the same credentials that are logged on. I had this same issue in 6.21.

The strange thing is that I have other task that run in batch and they go out and pull files from those very same folders without issue.
I also have an older scheduler (Autotask 2000)that runs the same task on the same server under the same logon and it doesn't have an issue triggering this way.

I am trying to migrate off of this older scheduler software (no longer supported)
I believe it has something to do with the way VC passes the credentials (with domain credentials maybe?) which the Iseries does not understand. It has a QPWDLVL System Value set to 0 on the Netserver.
This happens on 2003, 2008 and 2012 server.

Any ideas?

Have you set the File trigger to "polling mode"? Because I do not think it will work for your specific share without.

Also, can you verify that the Credential works by creating a File write Task and write to that specific folder you monitor (using same Credential).

---

Yes, Polling Mode (Samba Compatible) is checked.

I will test the file write later today. It sounds like you are suggesting that the userid needs write permissions to monitor a file for triggering? I'm pretty sure the userid that this job runs under only has read permissions, we don't currently have any jobs that write back to the Iseries, but I will create one to test.

Also I do have similar jobs that trigger off of files on Windows shares without issue.

You can use the File read Task. I was just interested in validating that the user can access this folder and file.

---

I created a write task and was able to write the file with no issue. It seems to be associated with polling.

We had a similar case some week ago. And it was indeed a version in 7.0.2 and earlier. We fixed this in 7.0.3. Are you sure that the server version is not older than 7.0.3?

---

The job was created in 6.21 but did not trigger correctly, but the VC server version has since been upgraded to 7.04.

I was able to solve a different issue by recreating the job from scratch in the 7.04 version, I am going to try that with this job as well and see if that helps.