Conference 7.286::digital

Steve,

As an ex-IPMT developer, what is it that you want to know? 
What is the context that you are prompting (text for some part
of a case, or for a filter)?

Basically, text strings need to be enclosed within quotes, so 
that they get parsed as a single unit. 

For example "this is a single text string", and "so 'is this'",
but "this "is not"".

You may also run into the VMS line length limit.

If the string is long, you may want to put it into a temporary file
[if you're doing case updates] and then use the 'text from' clause.

If you're doing a filter, then you just need to get the string
correct.

If you have any questions, feel free to send me mail directly.

Kathy Romberg

   Are there any defined patterns in the `IPMT case number' text string,
   such as pre-defined patterns of letters and numbers, and predefined
   punctuation in the string?  And what is the `architectued' maximum
   length of the IPMT case number text string?

   Educated guesses on the format, and a free-form text input routine that
   will accept most any string that resembles an IPMT case number, is one
   easy and obvious solution.  But a desire to perform some basic user
   input error checking is the reason this question arose.

   Also, the IPMT web pages -- if anybody has access to them -- need to
   be updated to reflect the current status and maintainers.  (If any.)

    Steve,
    
    Contact me offline, we in the PCBU have done some work with this and
    have been mildly sucessful.  The manuals are available in PS format
    on grocho::ipmt?  I'll check that out.
    
    What I have locally that I can send is:
    CORP_PROBLEM_ESCALATION_PROCESS.PS;3    IPMTGCM_CASE_FLOW.TXT;1
    IPMT_ADMIN_GUIDE_V1.PS;1                IPMT_COMMAND_DICT_014.PS;1
    IPMT_COMMAND_DICT_014.TXT;1             IPMT_FILTER_TEMPLATE_DOC.TXT;8
    IPMT_REPORT_DOC.TXT;2                   IPMT_USER_GUIDE_V1.PS;1
    MSEREP.DOC;1      
    
    In there we found the information we needed to query only the
    information we felt reletive.
    
    chet

   The string I'm encountering turns out to be an IPMT `Request ID' -- now
   off to figure out if these things have a documented format.

   Examples: HPAQ11P7C, ISO100287, EVT101972.

   Thanks for the pointers, and the off-line e-mail.

    
    
    What you are looking at here is log numbers created by local
    escalation outage systems. In Europe, ECSO is used and creates 
    number like this.
    
    However, ECSO feeds into the IPMT system which in turn creates a
    second log number, which is always in the format CFS.xxxxx where
    xxxxx is the unique id.
    
    Hope this helps...
    
    Have you tried http://grocho.ogo.dec.com:8010 ??
    
    I have a password if you require one, and some knowledge in operating
    this call handling system from Europe. Plus...plenty of contacts in 
    the IPMT world.
    
    	Cheers
    
    	Ian
    	
    	[email protected]@exchange
    	830-6130
    
    

    IPMT documentation is at MARX::IPMT$PUBLIC:.
    
    
    kathy

        In the US, the HPA number you are looking at is the field service
        log number generated by CHAMP or FIELD CHAMP.
        
        Dave Zaniewski

   This appears to be caused by another `escalation path' into OpenVMS
   engineering that few folks here in OpenVMS were even aware existed.
   (This path seems to have caught the folks that track problems entering
   and resolutions exiting OpenVMS by surprise.)

   We're going to see if we can get all problem reports routed via the
   existing IPMT-QAR bridge, which should eliminate some of the confusion
   and problems these IPMT Request IDs are/were creating.

   --

   much of the marx brothers IPMT engineering web site is outdated -- the
   webserver there has a number of things that appear to work fine, but
   much of the contact information presented at that site is woefully
   wrong.  Including an invalid webmaster e-mail address shown there...