HP OpenVMS Systems

Ask the Wizard

HP OpenVMS Systems

OpenVMS information

» What's new on our site
» Upcoming events
» Configuration and buying assistance
» Send us your comments

HP OpenVMS systems

» OpenVMS software
» Supported Servers
» OpenVMS virtualization
» OpenVMS solutions and partners
» OpenVMS success stories
» OpenVMS service and support
» OpenVMS resources and information
» OpenVMS documentation
» Education and training

Quick Links

» Non-javascript page
» Ask the Wizard

Test Drive OpenVMS

» OpenVMS I64 test drive
» Java test drive

Other information resources available to you include:

» OpenVMS freeware
» ECO kits, software and hardware support, prior version support
» Alpha SRM, ARC, and AlphaBIOS firmware updates
» ENCOMPASS - HP user group
» OpenVMS software downloads, OpenVMS freeware CD-ROM
» OpenVMS firmware locations
» DECconnect passive adaptor charts
» Cables reference guide
» MicroVAX console commands
» OpenVMS student research

Select a topic below to see Questions Frequently Asked by partners

» Using the online documentation library(installing BNU from the asap SDK)
» Global sections(how to create and use.)
» xx$CREATE_BUFOBJ system service(usage)
» Ethernet address(methods of determination)
» Shareable images(cookbook approach to creating one)
» Sharing data/code at absolute addresses(a guide with examples)
» Determining the Alpha microprocessor
» Using GETSYI to get hardware status

Evolving business value

» Business Systems Evolution
» AlphaServer systems transition planning
» Alpha RetainTrust program

Related links

» HP Integrity servers
» HP Alpha systems
» HP storage
» HP software
» HP products and services
» HP solutions
» HP support
disaster proof
HP Integrity server animation
HP Integrity server animation
Content starts here

Ask the Wizard Questions

Better Batch job control

The Question is:

I would like to know two things with regards to submitting
jobs to a batch que.

  1. Is there any way that I can submit a job in such a
     way that it will not run my LOGIN.COM?  I would
     surely think there must be a way to make it run like
     when I login with the /NOCOMMAND switch on.  I have
     exhausted all my resources for VAX tricks from every-
     body I know.

  2. When you submit a batch job, the log file gets its
     protections from some system defaults somewhere (I
     am guessing this part), rather than your own process
     default protection.  I would like to submit a batch
     job and have the .LOG file take on my default
     protections or let me specify the protections
     upon submission.

The Answer is:

    As with most things, the lack of direct availablility of these features
    on the SUBMIT command is a tradeoff between complexity of the interface
    and demand. However, it is possible to achieve these goals indirectly.

    1 - skip LOGIN.COM

      You can't skip LOGIN.COM completely, but you can implement your own
      message to control what sections are executed. Here's an example:


      Now, in LOGIN.COM, you can test the parameter value:

    	$ IF F$MODE().EQS."BATCH"
    	$ THEN
    	$       entry = F$GETQUI("DISPLAY_JOB","ENTRY_NUMBER",,"THIS_JOB")
    	$       P1 = F$GETQUI("DISPLAY_ENTRY","PARAMETER_1",entry,"")
    	$ ENDIF

    2 - control protection of log file

      The default SOGW protection mask for the log file is taken from the
      SYSGEN parameter RMS_FILEPROT.

      Without changing that parameter you cannot directly change the
      protection of the log file. However if you use a "jacket" procedure,
      you *can* adjust the protection of the "effective" log file. For example:


      Where JACKET.COM contains commands similar to:

    	$ SET PROTECTION=whatever you like
    	$ @realprocedure/OUTPUT=real-logfile "''p1'", "''p2'", "''p3'", -
    		"''p4'", "''p5'", "''p6'", "''p7'", "''p8'"

      If you wish to specify the protection on the SUBMIT command, you
      could use one of the parameters to pass the protection mask to
      the job. For example:

      	$ SET PROTECTION=('p2')

      Depending on your needs, you could make the jacket procedure generic,
      passing the name of the command procedure by parameter as well.

      Another option would be to direct the logfile to a particular
      directory which has a DEFAULT_PROTECTION ACE or OPTIONS=DEFAULT
      ACEs which specify your precise protection requirements. Similarly,
      creating a file with the same name as the log file and setting its
      security (SOGW and ACL) will result in that security profile being
      propogated to the new file. For example:


      See Section 8.1 in the V6 OpenVMS Guide to System Security (in
      particular Figure 8-1) for details of how OpenVMS decides on the
      ownership and protection of a file.