[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference cookie::archive_backup

Title:Archive/Backup
Moderator:COOKIE::MHUAIG
Created:Wed Sep 08 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:479
Total number of notes:2283

407.0. "Where do the info for ABS requests come from" by ATZIS2::ARCH_R (Raimund ARCH,MCS Austria *791/2259) Tue Mar 25 1997 11:01

    Hello,
    
    	this question has already been asked in entry 389
    	but as in abs$system:abs$policy_config.dat
    
    	ABS$POLICY_ENGINE_LOCATION   is defined to a Nodename
    
    
    	and in the request there is no such name i.e
    
    	Load "TAPE_5" on _GRZCLU$MKA600: write-enabled
    	Requested by:   ABS on  <<<-- ?
     	Owned by: ABS
    	Location: RECHNERRAUM
    
    	where does this information come from ?
    
    	Btw. SLS Requests gave the possibilities of changing the volume
    	or quitting the operation,like 
    
     Load volume 305209 on GMSCS::GMSCS$MUC1: write enabled
     - (first volume in volume set)
     - (required tape pool: SIMA34)
     - reply when ready, with volume name,
       NEW to get a new volume name or QUIT to abort job
    
    	is or will there be a way to get ABS asking a similar question
    	(at least if QUICKLOAD is set to 0) ?
    
    
    						Regards,
    						Raimund
T.RTitleUserPersonal
Name		DateLines
407.1COOKIE::HELLWIGThu Mar 27 1997 16:4759
    
>    	Load "TAPE_5" on _GRZCLU$MKA600: write-enabled
>    	Requested by:   ABS on  <<<-- ?
>     	Owned by: ABS
>    	Location: RECHNERRAUM
>    
>    	where does this information come from ?

Example:

Load "ABS001" on _KAWA$MKA500:
Requested by:   HELLWIG on FTA67:
Owned by: HELLWIG
Location: CXCORE8

The example above is a load request that I did outside of ABS.  You'll
notice that the requested by line is the username and the terminal device 
the user process is working from.  

ABS save/restore request jobs do not have a terminal device associated 
with it, the terminal device name is blank.  Below is the output from 
an ABS save request process.  

PLOW> show proc/all/id=226037AA

27-MAR-1997 13:38:12.40   User: ABS              Process ID:   226037AA
                          Node: PLOW             Process name: "SCHED#_9447"

Terminal:                     <<<<< Notice this is blank.
User Identifier:    [ABS]
Base priority:      4
Default file spec:  Not available


Because there is no terminal device associated with ABS, there is
nothing for MDMS to report for load requests.  


>    	Btw. SLS Requests gave the possibilities of changing the volume
>    	or quitting the operation,like 
>    
>     Load volume 305209 on GMSCS::GMSCS$MUC1: write enabled
>     - (first volume in volume set)
>     - (required tape pool: SIMA34)
>     - reply when ready, with volume name,
>       NEW to get a new volume name or QUIT to abort job
>    
>    	is or will there be a way to get ABS asking a similar question
>    	(at least if QUICKLOAD is set to 0) ?

ABS does not have anything that would perform this type of functionality.
What types of applications does it have, and why would you want to use
it?  The ABS storage class provides consolidation criteria.  The 
consolidation criteria (number of savesets, number of days, number of
volumes in a volume set) will start a new volume set once it has
reached it's consolidation criteria.  Is that the equivalent
functionality you are looking for?
    
Kim
407.2Quit SR without using ABSATZIS1::ARCH_RRaimund ARCH,MCS Austria *791/2259Tue Apr 01 1997 00:0117
    
    Hello Kim,
    
    thank you for your answers in .1.	
    
>	consolidation criteria (number of savesets, number of days, number of
>	volumes in a volume set) will start a new volume set once it has
>	reached it's consolidation criteria.  Is that the equivalent
>	functionality you are looking for?
    
    Consolidation criterias are ok.
    
    The customer was just asking if he is able to change the Operator
    Requests to have them like SLS Operator Requests because with those
    he was able to quit the SR with an Operator Reply.
    
    							Raimund
407.3COOKIE::HELLWIGWed Apr 02 1997 12:0921
    
>    The customer was just asking if he is able to change the Operator
>    Requests to have them like SLS Operator Requests because with those
>    he was able to quit the SR with an Operator Reply.
    
Is this something that is done frequently?  If so, I would be interested
in understanding why.  If it is an infrequent activity, the customer can
abort the scheduler job.  

  $ sched show job/brief/user=abs
  $ sched abort JOB_NUMBER

Note that if the save request is aborted, the volume that is being 
written to will be retired.  No more save requests will be written
to that volume (set).  This is because the volume is left in a 
state that ABS considers unrecoverable.  An example of an unrecoverable
state is the backup being aborted before the end of tape marks can
be written.

Hope this helps.
Kim