hai

Hi Rob,

What's in your batch4.com file ? when you execute $ pro "QUE4", "QUE4" is treated as a parameter for the pro command and it doesn't recognise it. I'm guessing that's why you received that error.

The first parameter should be the CO/DIV parameter which is an alpha-numeric of 3 characters. The second parameter should be the pro4 user id, also 3 characters.

I've execute the pro command in a VMS script using pro "LOG" "LOG" "function name", where LOG is a dummy CO/DIV and LOG is also a pro4 user ( just for running batch jobs ) and "function name" being another parameter.

To run a pro4 job from a VMS queue, don't you just submit your batch4.com file on a queue ? At the specified time/date, VMS executes batch4.com script which then logs into pro4 via pro command with appropriate parameters.

Hai

Erl,

What Jeff suggested in good and has worked well in Sungard because it was strictly controlled and software releases were cut every 3 to 4 months by the resident librarian. That way everybody knew when to expect the next release and planned accordingly.

The version control tool used there was just the rcs freeware on Unix. There are better version control software out there such as cvs and Clearcase.

Merging code in Pro-IV seems like more trouble than it's worth. Concurrent development in Pro-IV is more about better code/project management.

Hai