- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- DCL Synchronize command
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 12:36 AM
10-21-2003 12:36 AM
My problem is that the command does not work consistantly. It will work perfectly for 4 or 5 days and then simply fail. I have ensured that the next command procedure is submitted with the same user as the main procedure. I would really appreciate help with this problem.
Here is a sample of the code.
$ Submit/log=hisd_workdir:load_cerner1020.log -
/name=load_cerner/USER=CHAMBJX -
/param=("10/20/2003","1020") HISD_WORKDIR:LOAD_cerner_CHARGE
Job LOAD_CERNER (queue UPENN2_SYSBATCH, entry 3195) started on UPENN2_SYSBATCH
$!wait for load_cerner_charge to finish and check if it is successful
$ show time
21-OCT-2003 08:00:01
$ SYNCHRONIZE LOAD_CERNER
Thanks in advance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 12:52 AM
10-21-2003 12:52 AM
Re: DCL Synchronize command
the documentation of the SYNCHRONIZE command emphasizes the need for delete (d)
access of the job. Is there a chance that the job runs on diferent queues on
different opportunities? For example through a generic queue? That this queues
have different access rights? This might explain the strange bahavior!
Regards,
T. Pauli
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 12:58 AM
10-21-2003 12:58 AM
Re: DCL Synchronize command
I am willing to try just about anything at this point.
It does appear that when the job fails, it is smaller than the other times. I do not know if that would have any bearing or not.
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 01:28 AM
10-21-2003 01:28 AM
Re: DCL Synchronize command
As a side note, is there a way to extract/look at the DCLTABLE.EXE entries to see how the commands are defined?
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 01:31 AM
10-21-2003 01:31 AM
Re: DCL Synchronize command
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 01:33 AM
10-21-2003 01:33 AM
Re: DCL Synchronize command
Batch queue UPENN2_SYSBATCH, idle, on UPENN2::
/BASE_PRIORITY=10 /JOB_LIMIT=20 /OWNER=[1,4] /PROTECTION=(S:M,O:D,G:R,W:SD)
/RETAIN=ERROR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 01:40 AM
10-21-2003 01:40 AM
Solution$ SUBMIT ...
$ ENTRY = $ENTRY
$ SYNCHRONIZE/ENTRY='ENTRY'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 01:42 AM
10-21-2003 01:42 AM
Re: DCL Synchronize command
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 02:12 AM
10-21-2003 02:12 AM
Re: DCL Synchronize command
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 02:51 AM
10-21-2003 02:51 AM
Re: DCL Synchronize command
Other example:
$ renane temp.txt temp1.txt
works perfectly fine :-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 04:00 AM
10-21-2003 04:00 AM
Re: DCL Synchronize command
One possible workaround is to subm/retain=until="TOMORROW"
to make sure you sync against correct entry.
You might want to delete the entry at the end of your procedure to clean up the queue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 04:05 AM
10-21-2003 04:05 AM
Re: DCL Synchronize command
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 09:03 AM
10-21-2003 09:03 AM
Re: DCL Synchronize command
Batch queue UPENN2_SYSBATCH, idle, on UPENN2::
/BASE_PRIORITY=10 /JOB_LIMIT=20 /OWNER=[1,4] /PROTECTION=(S:M,O:D,G:R,W:SD)
/RETAIN=ERROR
Adding W:SD allows anyone on the system to submit (S) to the queue and delete (D) any job in the queue. The delete access you need is already available with O:D (owner of job may delete it).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 05:33 PM
10-21-2003 05:33 PM
Re: DCL Synchronize command
I have same problem. Some year ago I've used SYNCHRO command but DCL procedure sometimes fails; now I don't remember the reason but now I use a DCL procedure to synchonize work.
You can see the example DCL procedure that you can change.
If you are interesting I can search in my old documentation to discover exactly reason of this problem.
Bye
Antoniov
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2003 05:36 PM
10-21-2003 05:36 PM
Re: DCL Synchronize command
file .com means binary in windows; you cannot see attachment.
Now I changed name to SYNCHRO.TXT.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2003 12:23 AM
11-11-2003 12:23 AM
Re: DCL Synchronize command
Many thanks! I have made several modifications to the command procedure but the following seems to have fixed/worked around the problem.
I added a 30 second delay before the synchronize command to give the job controller time to get everything set up and open. I also am using the entry number vice the name in the procedures.
Again, many thanks to all who responded.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2003 12:52 AM
11-11-2003 12:52 AM
Re: DCL Synchronize command
Sumbit som point to Pauli has helped giving a good idea.
Bye
Antoniov