All symbols used in the filespec used in the SUBMIT command are set within the procedure itself. Actually, it's just one: "here", derived from:
$ me=f$environment("procedure")
$ here=f$parse(me,,,"DEVICE")+f$parse(me,,,"DIRECTORY")
so a difference in f$mode() is not the problem here. As stated before, using the immediate output of f$environment has been used, both with, and without, "NO_CONCEAL" option in f$parse, without result.
And as the logfile output shows - with VERIFY enabled - all symbol translations are done - and properly.
LinkCount=1 holds for all files - even in SYS$LOGIN, which is another disk. Second, this is a 7.3-2 system.
So that isn't the cause either.
This is, indeed, a cluster. The queue used in the SUBMIT command is a logical, referring to a local queue, set autostart on that node only, not on both nodes:
Node1> sho log sys$batch
"SYS$BATCH" = "SYS$BATCH_NODE1" (LNM$SYSTEM_TABLE)
and
Node2> sho log sys$batch
"SYS$BATCH" = "SYS$BATCH_NODE2" (LNM$SYSTEM_TABLE)
Apart from the node name, the queue definitions are equal:
Nodex> sho queue/full sys$batch
Batch queue SYS$BATCH_NODEx, idle, on NODEx::
/AUTOSTART_ON=(NODEx::) /BASE_PRIORITY=4 /JOB_LIMIT=4 /OWNER=DEV
/PROTECTION=(S:M,O:D,G:R,W:S)
...
so if I submit the procedure to SYS$BATCH on node1, it will execute on node1 - and not on node2. That would, I think, rule out a difference in logicals and disks.
Nevertheless, I checked logicals on both systems; The device in the SUBMIT command refers the same device on both systems; this is a shadowed disk, that resides on a SAN; WWID's are the same on both systems (as it should be)
Willem Grooters
OpenVMS Developer & System Manager
