Maintenance Checklist 3

[PhoneGuyy]

Does anybody have a simple monthly or quarterly checklist that they do on Option 11, 61 and 81?

I have reade GHTrout already, but was looking to see what others are doing also...

Like a simple excel spreadsheet or something...

 

[RyanEOD]

Wow, reminding me of the PMI days back in the Air Force. Wish I had a copy of those, they were the best. If anyone has them they would be a great thing to have for a Maintenance Checklist, Schedule, Instructions.

 

[Tigernach]

I have one... I use it for my quarterly and semi annual checks for my customers. Give me a call..

 

[Dphone]

Would you post it please?

 

[johnpoole]

here's a short script that i run every day.. you'll need to edit it to match your cequ

proc main


transmit "****^M"
mspause 10


CAPTURE ON

transmit "ld 32^M"
 
    waitfor "."  forever
transmit "LDIS 4 0^M"
    waitfor "."  forever
   
transmit "LDIS 4 1^M"
    waitfor "."  forever
transmit "LDIS 8 0^M"
    waitfor "."  forever
transmit "LDIS 8 1^M"
    waitfor "."  forever
transmit "LDIS 20 0^M"
    waitfor "."  forever
transmit "LDIS 20 1^M"
    waitfor "."  forever
    
transmit "LDIS 24 0^M"
    waitfor "."  forever
 transmit "LDIS 24 1^M"
    waitfor "."  forever   
    
transmit "LDIS 32 0^M"
    waitfor "."  forever   
transmit "LDIS 36 0^M"
    waitfor "."  forever
transmit "LDIS 40 0^M"
    waitfor "."  forever 
transmit "LDIS 52 0^M"
    waitfor "."  forever
transmit "LDIS 52 1^M"
    waitfor "."  forever
transmit "LDIS 56 0^M"
    waitfor "."  forever             
transmit "LDIS 56 1^M"
    waitfor "."  forever
transmit "LDIS 64 0^M"
    waitfor "."  forever 
transmit "LDIS 68 0^M"
    waitfor "."  forever
transmit "LDIS 68 1^M"
    waitfor "."  forever       
transmit "LDIS 72 0^M"
    waitfor "."  forever		
transmit "LDIS 84 0^M"
    waitfor "."  forever 
transmit "LDIS 88 0^M"
    waitfor "."  forever 
transmit "LDIS 88 1^M"
    waitfor "."  forever  
transmit "LDIS 96 0^M"
    waitfor "."  forever
transmit "LDIS 100 0^M"
    waitfor "."  forever   
transmit "LDIS 104 0^M"
    waitfor "."  forever
transmit "LDIS 112 0^M"
    waitfor "."  forever 
transmit "LDIS 112 1^M"
    waitfor "."  forever 
transmit "LDIS 116 0^M"
    waitfor "."  forever
transmit "LDIS 116 1^M"
    waitfor "."  forever 
transmit "LDIS 120 0^M"
    waitfor "."  forever
transmit "LDIS 120 1^M"
    waitfor "."  forever 
transmit "LDIS 128 0^M"
    waitfor "."  forever
transmit "LDIS 128 1^M"
    waitfor "."  forever    
transmit "LDIS 132 0^M"
    waitfor "."  forever
transmit "LDIS 136 0^M"
    waitfor "."  forever
transmit "LDIS 144 0^M"
    waitfor "."  forever    
transmit "LDIS 148 0^M"
    waitfor "."  forever
transmit "LDIS 152 0^M"
    waitfor "."  forever



transmit "****^M"     
transmit "ld 60^M"
 
    waitfor "."  forever  
    
    transmit "lcnt^M" 
    
    waitfor "."  forever 
  CAPTURE OFF    
    transmit "****^M"      
  
endproc

that gives me all disabled sets, i prt those a send an out of service to the help desk to generate a trouble.. either one of the techs finds the set and plugs it in or deletes the tnb... it also list the lcnt, which i look at for pri errors.. one a week i do an inv prt sets (ld 117) then use an excel macro to compare the as built with the actual.. that catches users trying to do free upgrades..


once a quarter i prt a complete tnb and use pepedogs macro to sort it.. that helps est a history... if someone outs a phone, i have a record of the tn... i also use that to check that all dn's cfw/hta to mail have a mb..

i check the cp once a month for any disabled boxes or users that have not logged into mail in over 30 days... in both cases i remove the boxes and the forwarding on the set..

once a quarter i print the pickup groups to see if any pickup groups are in split buildings.. we have 16 remotes.. so i catch member of the same rnpg, 10 miles apart.. so by des and tn we try to police the rnpg's... that is needed due to non techs doing a set copy..

90 percent of my maint is a direct result of in house techs making mistakes..

i check both the symposium and mail for troubles.. the symposium is usually full of reports that can not print.. supervisors schedule reports with a bad download path.. so those schedules get blown away...

john poole
bellsouth business
columbia,sc

 

[RyanEOD]

John,

AWESOME information, star, but can you give more info on the Macros you run. . I have never done any of those and would like to start looking at them.

 

[RyanEOD]

Hummm . . trying to use pepedogs macro's . . . and it seems that they don't work too well on 5.0 with the2004p2's and whatnot. I downloaded the macro from his website so I assume it is the most current. It is v2.19. Anyone have any suggestions?

 

[RyanEOD]

NM . . . I found an edit to the Macro's on GH's website.

 

[GHTROUT]

Another maintenance checklist is to make sure your Midnight Routines have all you want, then either review the output or invoke it with LD135 .MIDN

Personally, I too like the idea of a script to run various inquiries.




~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]