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

Conference kernel::csguk_systems

Title:CSGUK_SYSTEMS
Notice:No restrictions on keyword creation
Moderator:KERNEL::ADAMS
Created:Wed Mar 01 1989
Last Modified:Thu Nov 28 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:242
Total number of notes:1855

136.0. "The ECSO & CLD Topic" by KERNEL::ADAMS (Venusian turned Aquanaut,-833 3790) Tue Apr 23 1991 14:11

    
    
    This topic is for use by members of the Systems Diagnosis group
    
    to cover the  topics of   ECSO  & CLD's
    
T.RTitleUserPersonal
Name
DateLines
136.1London ECSO Member changes.KERNEL::ADAMSVenusian turned Aquanaut,-833 3790Tue Apr 23 1991 14:1957
	
     I have been advised by Dave Goodwin, the Local ECSO Manager for London, 
     of the following changes to ECSO Members on LONLOG as part of the front 
     end restructuring.  Please use the new Member short codes or id's from 
     now on, the replaced Members listed below are not to be used.


     New Members:- (To be used from now on)
    
     MEMBER      SHORT  MEMBER NAME            NODE     LEVEL   TYPE 
     ID          CODE  

     72WA        LRA    London RC Res W        LONLOG     1      R
     72WB        LRB    London RC Res C        LONLOG     1      R
     72WC        LRC    London RC Sys W        LONLOG     1      R
     72WD        LRD    London RC Sys C        LONLOG     1      R
     72WE        LRE    London RC Off W        LONLOG     1      R
     72WF        LRF    London RC Off C        LONLOG     1      R
     72WG        LRG    London RC Term W       LONLOG     1      R
     72WH        LRH    London RC Term C       LONLOG     1      R


     Replaced Members:- (No longer used)

     MEMBER      SHORT  MEMBER NAME            NODE     LEVEL   TYPE
     ID          CODE
    
     75C         CDD    CITY DISTRICT SUPP     LONLOG     2      R         
     75CA        TLC    City team leader       LONLOG     1      I              
     75CB        CDB    CITY SYSTEMS HONE      LONLOG     1      R  
     75CC        CDC    CITY SYSTEMS EVANS     LONLOG     1      R         
     75CG        CDG    CITY SYS (NICHOLSON)   LONLOG     1      R         
     75CK        CDK    CITY SYSTEMS SCOTT     LONLOG     1      R         
     75CX        CEX    city_exceptions        LONLOG     1      R         
     7J6A        TLH    Lon high vol team      LONLOG     1      I         
     7J6S        CDS    CITY QBUS              LONLOG     1      R         
     7J6V        CDV    CITY TERMS & PC'S      LONLOG     1      R         
     7J6X        HIX    London_hi_vol_except   LONLOG     1      R         
     7P8         WED    WEST END DISTRICT      LONLOG     2      R         
     7P8A        TLW    Lon West Team Leader   LONLOG     1      I         
     7P8D        WEV    W.E. DEVICE SPECS      LONLOG     1      R         
     7P8I        WEI    WEST END INSTALLS      LONLOG     1      R         
     7P8J        WEJ    W.E. SYS (BARRETT)     LONLOG     1      R         
     7P8N        WEN    W.E. SYS (HORGAN)      LONLOG     1      R         
     7P8X        WEX    west_exceptions        LONLOG     1      R         
     7P8Y        WEY    W.E. SYS (MCDONALD)    LONLOG     1      R         
     7P9S        WES    WEST END QBUS          LONLOG     1      R         
     7P9T        WET    WEST END TERMS & PCS   LONLOG     1      R         
 
     Should you have any queries regarding the above information, please
     do not hesitate to contact me on x3339.

     Best regards

     Cindy Park
     IT SUPPORT.

136.2inc ooh.cldKERNEL::HOCKLEYTue Apr 23 1991 15:191
    
136.3OOH CLD ProcessKERNEL::HOCKLEYTue Apr 23 1991 15:20108
This request could come from a Duty Manager in the UK or a Regional Exception 
Manager for the Northern European Countries (Finland, Sweden, Norway, Denmark, 
Holland or Belgium). They will be required to supply all the relevent 
information supplied to you, preferably in a mail file but it could be verbally 
or via an ECSO call. 

NO qualification of the call is required. If the Manager wants a CLD logged - 
log it.

Below is the step by step method.


                  ***  Both CLD and ECSO run from THESUN  ***   
		  ***     Your Account Name is CSC_DM     ***

Logging a CLD....


        1)   Enter ECSO, at command line type UNI ULD. Check group for 
	     ECSO entry of call to be CLD'd.  If no entry on ECSO
             open an ECSO call from the group member, ULD.  
	
	     To log a problem on ECSO, type LOG at the command prompt.
	     This will display a blank call screen, complete the screen 
	     by using TAB to step between fields (backspace will take 
	     you backwards).
	    
	2)   Complete management screen accordingly. Enter Support 
	     Engineer as Resource Manager.  
             The respective Managers names, Phone number and ECSO member
	     must be supplied to you.

	3)   Add/Edit to include CLD template as necessary.
	     It may be that you will not have a completed template, but 
	     you will need to add AT LEAST a valid problem statement and 
	     criticallity statement.

        5)   Exit from edit screen - control Z or Gold E - select C to check 
	     word wrap, edit if necessary, exit from screen and select E to 
	     end edit session.

    	6)   REQ ULC - this will open the CLD and automatically update ECSO
 	     with the CLD number. The CLD number will be given at the bottom
	     of the screen once process completed.
	    
 	7)   Exit from ECSO (Gold E or Exit, at the Command Line), and type
	     CLD at the $ prompt. At CLD main menu, S to send CLD to CSSE. 
	     It will prompt you for the CLD number. Enter CLD nember 
	     - last five digits.
	
	8)   Mail Mick Hockley (KERNEL::HOCKLEY) with details of the Customer
	     name CLD logged for, to allow recognised procedures to be invoked.
	   
 

Customer:                                             System :     
Street  :                                             Ser-Nr.:     
City    :                                             Option : ........ Note 1
Contact :                                             Tel-Nr.: 
Branch  :                             Date 18-MAR-91  Log-Nr.: ........ Note 2
RD-Tel-Nr:                  Onsite:                   Standby:                

>>> Priority Code :  <<<

Prob. Mgr: xxxxx xxxxxxxx               Tel-Nr.: DTN-8xx-xxxx     ID: XXX Note 3
Tech. Mgr: xxxxx xxxxxxxx               Tel-Nr.: DTN-8xx-xxxx     ID: XXX  "   " 
						   	  /
						  Note 4 / 
Esc. Mgr L1:                            Tel-Nr.:         |        ID:     
Esc. Mgr L2:                            Tel-Nr.:         |        ID:     
Esc. Mgr L3: xxxxx xxxxxxx              Tel-Nr.: DTN-8xx-xxxx     ID: XXX  "  "  
Esc. Mgr L4:                            Tel-Nr.:                  ID:     
Esc. Mgr L5:                            Tel-Nr.:                  ID:     

Res. Mgr  1: Support Engineer Note 5    Tel-Nr.: DTN-8xx-xxxx     ID: XXX  "  "     
Res. Mgr  2:                            Tel-Nr.:                  ID:     

Accnt.Rep:                              Tel-Nr.:                  ID:     

CLD Log Nr.:          AFSG Log Nr.:          Other.:                     

Involved member(s):
------------------ 

EG  A/R   3 ULD N/I   3 

Current escalation level: 5 (  3 days)

Problem:
------- 

Plan(s):
------- 

	*****************************************************************
	* NOTES:-							*
	* 1) The failing option is to be entered here			*
	* 2) The log number can be over-written with a local number, if *
	*    required, ie. TSC Log number etc.				*
	* 3) Enter ECSO member ID, if known.				*
	* 4) Enter phone numbers in this format to allow correct        *
	*    transfer to the CLD database.				*
	* 5) Enter the Support Engineer details here to allow correct	*
	*    transfer to the CLD database.				*
	*****************************************************************	
 

    
136.4outstanding ECSO callsKERNEL::PETTETNorm Pettet CSC BasingstokeThu Jul 04 1991 11:3815
    Hello,
    
    
    	Recently we had a situation whereby a software CTSC call was at
    level #5 (awaiting tape) for greater than 1 week. As it turned out the
    customer had logged 2 calls for the same crash and Dave Gledhill had
    already done the business. To avoid a similar situation arising again
    can the following procedure be followed namely:-
    
    The person on E.C.S.O duty monitors the CTSC queue#9. If there is an
    outstanding call for greater than 1 week please ring customer and
    determine if the tape has been sent or not. 
    
    Cheers....Norm Pettet