Setting VMS logicals from Quick

[Chris Sharman]

>I've tried doing a run command "$DEASSIGN/JOB"   between the DEFINEs and
>that works, but the second DEFINE still doesn't work.  This I know from
>stepping through in debug and using "$show logical TAB$SUBJ$AREA"
>
>Any ideas why redefining the logical doesn't work?
>Any suggestions for an alternative strategy?  
>Although it works at the first attempt if the file exists, is it even a
>valid technique to declare a file before it's specification is known?  I
>didn't write this program;-)

You seem to have solved the problem, but the question of whether it's valid to
declare a file before defining the necessary logical is interesting.

I'd always assumed it wasn't. We use logicals to implement customer-specific
price files for certain customers, rather than the default file, but we've
always made users come all the way out of Quick to change files.

Can anyone say when it's valid to change the logicals ?
My screen does an explicit getsystemval to display which file it's got, in
addition to the implicit translation done to open the file. I'd hate for them
to get out of synch, and I'd always assumed that once you'd got to the screen
it was too late to change, and also that the second open would use the context
of the first open rather than re-translating.

PS: I'd have thought getsystemval & setsystemval preferable to 'run command...'


______________________________________________________________________
Chris Sharman			Chris.Sharman@CCAgroup.co.uk
CCA Stationery Ltd, Eastway, Fulwood, Preston, Lancashire, PR2 9WS.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.