Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

/log is not displayed in output ---why??

 
SOLVED
Go to solution
Mrityunjoy Kundu
Frequent Advisor

/log is not displayed in output ---why??

I m sending you com file attached with this mil ,where you find many commnd with /log qualifier.But in the output /log message is not displayed ..why??

7 REPLIES
Thomas Ritter
Respected Contributor

Re: /log is not displayed in output ---why??

Maybe a symbol scoping problem ?
What do "pu" and "ren" equate to ?
Prehaps at the start of procedure try

$ purge:= purge
$ rename := rename


Like the use of "inquire".
Jon Pinkley
Honored Contributor
Solution

Re: /log is not displayed in output ---why??

You don't give us a log of what's not working.

Did you look in concert$command:ShutCommon.com to see if it is redefining any commands?

Since you don't tell us what specific command isn't working, I will guess it is the delete command.

Both the DELETE and PURGE verbs have DELETE as the image to run. Has someone defined a logical DELETE that is causing the DELETE command to execute a different image?

So right before your delete command do a

$ show symbol delete ! see if command modified
$ show logical delete ! is DELETE command using DELETE.EXE?

If these are both normal, then it is possible, (but unlikely) that someone has modified the command definition for delete. To see that, you will need the VERB utility from the freeware.
it depends
Heinz W Genhart
Honored Contributor

Re: /log is not displayed in output ---why??

Hi mrityunjoy

It would be very helpful, if you could specify more exactly, where your problem is.

Another thing is that we can see, that you have assigned points to only 30 of 81 responses to your questions. You may read http://forums1.itrc.hp.com/service/forums/helptips.do?#34
It would be more motivating to answer your questions, if you could find the time to assign points to those who helped you with their answers.

Geni
Mrityunjoy Kundu
Frequent Advisor

Re: /log is not displayed in output ---why??

Suppose, there is a line

backup dk$acjrnl1:[acjrnl1]cala.pos_jrnf; DK$ACJRNLBCK:[acjrnlbck1]cala.bak_jrnf; /lo

here /log should determines whether file specification of each file processed is displayed on sys$output during this operation..but in the above mentioned com file we donot find any informtionl message in sys$output
Wim Van den Wyngaert
Honored Contributor

Re: /log is not displayed in output ---why??

And did you see the text
Accounting journal Backup completed successfully ?

Wim
Wim
The Brit
Honored Contributor

Re: /log is not displayed in output ---why??

Check whether messaging is turned off, or sys$output is redefined!

Dave.
Jon Pinkley
Honored Contributor

Re: /log is not displayed in output ---why??

I think Dave (The Brit) has it. It's the simplest plausible explanation. Give him 10 points.

Contents of mess_state.com
___________________

$! demo demonstrating what Dave (The Brit) guessed is the problem
$! The Brit Jul 24, 2007 12:27:29 GMT Unassigned
$!
$! --------------------------------------------------------------------------------
$! Check whether messaging is turned off, or sys$output is redefined!
$!
$! Dave.
$!
$ this_proc = f$environment("procedure")
$ oldmsg = f$environment("message")
$ write sys$output "Message state on entry to ''this_proc' is ''oldmsg'"
$ set message/facility/identification/severity/text ! explicitly turn messaging on
$ set sec/def 'this_proc'/log ! should generate log message
$ set message/nofacility/noidentification/noseverity/notext ! explicitly turn messaging off
$ set sec/def 'this_proc'/log ! No log displayed because messaging off
$ set message 'oldmsg'
$ set sec/def 'this_proc'/log ! should generate log message

________________________________


$ set nover
$ @mess_state
Message state on entry to ROOT$USERS:[JON.SCRATCH]MESS_STATE.COM;6 is /FACILITY/SEVERITY/IDENTIFICATION/TEXT
%SET-I-MODIFIED, ROOT$USERS:[JON.SCRATCH]MESS_STATE.COM;6 modified
%SET-I-MODIFIED, ROOT$USERS:[JON.SCRATCH]MESS_STATE.COM;6 modified
$ set ver
$ @mess_state
$! demo demonstrating what Dave (The Brit) guessed is the problem
$! The Brit Jul 24, 2007 12:27:29 GMT Unassigned
$!
$! --------------------------------------------------------------------------------
$! Check whether messaging is turned off, or sys$output is redefined!
$!
$! Dave.
$!
$ this_proc = f$environment("procedure")
$ oldmsg = f$environment("message")
$ write sys$output "Message state on entry to ROOT$USERS:[JON.SCRATCH]MESS_STATE.COM;6 is /FACILITY/SEVERITY/IDENTIFICATION/TEXT"
Message state on entry to ROOT$USERS:[JON.SCRATCH]MESS_STATE.COM;6 is /FACILITY/SEVERITY/IDENTIFICATION/TEXT
$ set message/facility/identification/severity/text ! explicitly turn messaging on
$ set sec/def ROOT$USERS:[JON.SCRATCH]MESS_STATE.COM;6/log ! should generate log message
%SET-I-MODIFIED, ROOT$USERS:[JON.SCRATCH]MESS_STATE.COM;6 modified
$ set message/nofacility/noidentification/noseverity/notext ! explicitly turn messaging off
$ set sec/def ROOT$USERS:[JON.SCRATCH]MESS_STATE.COM;6/log ! No log displayed because messaging off
$ set message /FACILITY/SEVERITY/IDENTIFICATION/TEXT
$ set sec/def ROOT$USERS:[JON.SCRATCH]MESS_STATE.COM;6/log ! should generate log message
%SET-I-MODIFIED, ROOT$USERS:[JON.SCRATCH]MESS_STATE.COM;6 modified
$
it depends