[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
|
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
637.0. "Housekeeping procedures scheduled twice." by BACHUS::BERVOETS (Luc Bervoets - CSC Brussels alive and kicking) Wed May 06 1992 17:19
Hello,
I have a problem with ALL-IN-1 Housekeeping procedure .
When the system is rebooted, the housekeeping procedure are scheduled
twice. I know that there is a problem with embedded spaces, but this
isn't the case at this customer.
He is running VMS 5.5 and ALL-IN-1 V2.4 (K603).
Is this perhaps a problem with the new VMS queue management system?
Included you will find the entries in the batch queue and also the info
of how the procedures were scheduled.
Batch queue A1$BATCH, available, on COV02::
/BASE_PRIORITY=0 /NOENABLE_GENERIC /JOB_LIMIT=10 /OWNER=[VMS,SYSTEM] /PROTECTION=(S:E,O:D,G:R,W:W) /WSDEFAULT=1024 /WSEXTENT=8192
/WSQUOTA=3072
Entry Jobname Username Status
----- ------- -------- ------
39 PRELIM_TEST_OF_FC
ALLIN1 Holding until 8-MAY-1992 01:00
Submitted 6-MAY-1992 00:04 /KEEP /LOG=$1$DUA22:[ALLIN1.LOG]OA$SM_PRE_TEST_OF_FILE_CAB.LOG1992050801000000; /PARAM=("PT",
"1992050801000000","OA$LIB:OA$SM_FCVR_PRE_PHASE1_SCHEDULE.COM","MANAGER") /NOPRINT /PRIORITY=100
File: _$1$DUA22:[ALLIN1.LIB_ENGLISH]SMJACKET.COM;4
499 PRELIM_TEST_OF_FC
ALLIN1 Holding until 8-MAY-1992 01:00
Submitted 1-MAY-1992 01:00 /KEEP /LOG=$1$DUA22:[ALLIN1.LOG]OA$SM_PRE_TEST_OF_FILE_CAB.LOG1992050801000000; /PARAM=("PT",
"1992050801000000","OA$LIB:OA$SM_FCVR_PRE_PHASE1_SCHEDULE.COM","MANAGER") /NOPRINT /PRIORITY=100
File: _$1$DUA22:[ALLIN1.LIB_ENGLISH]SMJACKET.COM;4
Manage Housekeeping Procedures
(Selections: 0 ) (New messages: )
No. Date and Time Proc. Description Current status Frq
1 08-May-1992 01:00am PT PRELIM_TEST_OF_FC Waiting to run 7
Move to item, and enter option (press GOLD MENU to see options, or HELP for
more information)
Scheduled Utility
Schedule key: 1992050801000000 Utility name: PT
Procedure name for this particular utility: PRELIM_TEST_OF_FC
Utility time: 08-May-1992 01:00am Reschedule frequency: 7
Batch queue entry number: 39 Batch queue: A1$BATCH
Manager's log: OA$LOG:OA$SM_PRE_TEST_OF_FILE_CAB.LOG1992050801000000
Admin's log: OA$LOG:OA$SA_PRE_TEST_OF_FILE_CAB.LOG1992050801000000
Completed: Current status: Waiting to run
Actual start time of run:
Node utility ran on:
Account to receive status reports: MANAGER
Name of account that scheduled utility: MANAGER
SYSTEM MANAGEMENT/ADMINISTRATOR UTILITY MASTER FILE
Utility Name: PT
Utility Description: Preliminary Test of File Cabinets
Utility Command File: OA$LIB:OA$SM_FCVR_PRE_PHASE1_SCHEDULE.COM
Default Batch Queue: A1$BATCH
SM Log Name:OA$LOG:OA$SM_PRE_TEST_OF_FILE_CAB.LOG
SA Log Name:OA$LOG:OA$SA_PRE_TEST_OF_FILE_CAB.LOG
Account To Run Utility Under: MANAGER
Account To Receive Reports: MANAGER
Default Reschedule Frequency: 0
Name of Schedule Form: SM_SKEDFORM_FCVR_PRE_PHASE1
Name of Schedule Script: SM_SKEDSCRIPT_DEFAULT.SCP
Name of Utilty Boilerplate Name: SM_FCVR_PRE_PHASE1_BLP
Shutdown Flag: 0 SA Can Schedule Flag: 1 SA Can Display Info: 1
FCVR Policies
Orphans:1=List,2=Delete: Recovered msgs acnt: MANAGER
Check body files: 1
SAM Policies
Create New Dirs Flg: Number of Dirs to Create:
Disk & Directory To Create Shared Directories in:
T.R | Title | User | Personal Name | Date | Lines |
---|
637.1 | Help on analyzing | UTRTSC::BOSMAN | We're just sugar mice in the rain | Thu May 07 1992 08:29 | 46 |
| Luc,
I don't have a direct answer, but some ideas that may help
investigating this one.
Copy OA$LIB:SM$BATCH$CLEANUP to your OAUSER directory and rename it,
let's say to SBC.SCP. Modify SBC to do only the checking, and not the
submitting again (last four lines should look like):
| \\ .IF #ENTRY EQS "" THEN GET #SKED_TYPE = "1" -
| \\\\ .text "Requeueing " #util_name " on " #util_queue
|
|BIND_BREAK *QUI
|.EXIT
Cut and execute the part form A1V24START that checks for rescheduling
and modify it to:
|$ ALLIN1 /NOINIT /OVERRIDE
|Display "" ALL-IN-1 is RUNNING""
|OA$FLO_OPEN_LIB OA$LIB:MANAGER
|OA$FLO_OPEN_LIB OA$LIB:ADMIN
|DO SBC
Running this procedure with trace enable might help you what is going
wrong here. Now your able to check the different equations in SBC.SCP
to see which one is causing the trouble:
|BIND *QUI TO QUI$QUEUE_JOB:"BATCH,TIMED_RELEASE_JOBS" -
| WITH .ENTRY_NUMBER NES ""
or some part of:
|FOR SM_GEN_UTI_SCH -
| WITH (.SA_UTIL_SCHED GTS oa$date_nbs and .SA_UTIL_CUR_STS EQS "0") do -
or some part of:
| \\ FOR FIRST *QUI WITH .JOB_NAME == #UTIL_NAME AND -
| .JOB_QUEUE_NAME == #util_queue DO -
| GET #ENTRY = .ENTRY_NUMBER -
| \\ .IF #ENTRY EQS "" THEN GET #SKED_TYPE = "1" -
| \\\\ .text "Requeueing " #util_name " on " #util_queue
FWIW, Sjaak.
|
637.2 | | RTOEU::JGIBBONS | | Fri May 08 1992 11:21 | 16 |
| The probelems aren't just with embedded spaces (in fact I thought spaces in
the procedure name were ok, but my memory might be playing tricks on me).
I've had this problem with an apostrophe in the procedure name. From memory
that was stripped out from the job name, but the procedure name still had it
so when the system reboot it checked for housekeeping jobs that needed requeuing
and didn't find a match in the batch queue for the procedure and so resubmitted
it.
I may have got some of the details back to front (it seems such a long time ago)
but I know I raised the issue in a previous incarnation of this notes file
(probably under the username NEWOA::GIBBONSJ in case you want to look for it.
Jenny
|
637.3 | Note 23 | UTRTSC::BOSMAN | We're just sugar mice in the rain | Fri May 08 1992 12:14 | 7 |
|
See also note 23. That quote problem is still on V3.0 systems. There
weren't any replies (?).
But I don't think it's the problem Luc has.
Sjaak.
|
637.4 | See Note 1967 - you are using long job names | AIMTEC::GRENIER_J | | Thu Dec 17 1992 19:54 | 6 |
| Perhaps you are experiencing the same problem we had here with the
long job names.
Jean
(problem actually resolved by Iain).
|