Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointer To FileMan Files |  Fields |  Found Entries |  All
Print Page as PDF
Global: ^%ZTER(3.077

Package: Kernel

Global: ^%ZTER(3.077


Information

FileMan FileNo FileMan Filename Package
3.077 ERROR TRAP SUMMARY Kernel

Description

Directly Accessed By Routines, Total: 8

Package Total Routines
Toolkit 5 XTERSUM    XTERSUM1    XTERSUM3    XTERSUM4    XUCT    
Kernel 1 %ZTER    

Accessed By FileMan Db Calls, Total: 3

Package Total Routines
Toolkit 3 XTERSUM    XTERSUM1    XTERSUM3    

Pointer To FileMan Files, Total: 4

Package Total FileMan Files
Kernel 4 TASKS(#14.4)[#3.07701(14)]    OPTION(#19)[#3.07701(12)]    PACKAGE(#9.4)[3.1]    NEW PERSON(#200)[#3.07701(11), #3.077031(.01)]    

Fields, Total: 14

Field # Name Loc Type Details
.01 ERROR TEXT 0;1 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>60!($L(X)<3)!'(X'[U) X
  • LAST EDITED:  MAR 05, 2008
  • HELP-PROMPT:  Answer must be 3-60 characters in length
  • DESCRIPTION:  This is the text captured with the error. It is a means of providing a common key for the errors to be clustered under. Each one will has a series of characteristics which will be captured for later analysis even after
    the error has been purged off of the ^%ZTER global.  The first date and time is stored as will be the most recent occurrence.
  • TECHNICAL DESCR:  
    This string will be parsed off of the $ZE sting.  If the string is not there, then an "[Unknown Xecute]" will be created to store these cases.
  • CROSS-REFERENCE:  3.077^B
    1)= S ^%ZTER(3.077,"B",$E(X,1,30),DA)=""
    2)= K ^%ZTER(3.077,"B",$E(X,1,30),DA)
  • CROSS-REFERENCE:  3.077^C^KWIC
    1)= S %1=1 F %=1:1:$L(X)+1 S I=$E(X,%) I ",~<>():;"[I S I=$E($E(X,%1,%-1),1,30),%1=%+1 I $L(I)>2,^DD("KWIC")'[I S ^%ZTER(3.077,"C",I,DA)=""
    2)= S %1=1 F %=1:1:$L(X)+1 S I=$E(X,%) I ",~<>():;"[I S I=$E($E(X,%1,%-1),1,30),%1=%+1 I $L(I)>2 K ^%ZTER(3.077,"C",I,DA)
    3)= Used to make lookup easy
1 FIRST DATE/TIME 0;2 DATE

  • INPUT TRANSFORM:  S %DT="EST" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  MAR 05, 2008
  • DESCRIPTION:  
    This is the first date and time that the error has occurred.  It is of historic importance and can be used to find the causative event of the error that is being reported.
2 MOST RECENT DATE/TIME 0;3 DATE

  • INPUT TRANSFORM:  S %DT="EST" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  MAR 24, 2009
  • DESCRIPTION:  
    This is the most recent time that the situation has happened.  It is important in that it is the most likely to still be in the error trap global, ^%ZTER.
  • TECHNICAL DESCR:  As this gets updated, the date is compared with the date/time stored here. This will help to identify any items which may need to be accessioned into this summary. It may also be used to help purge any errors which have
    not been active in a long time (and perhaps is now obsolete code).
3 ROUTINE NAME 0;4 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>20!($L(X)<2) X
  • LAST EDITED:  MAR 05, 2008
  • HELP-PROMPT:  Answer must be 2-20 characters in length.
  • DESCRIPTION:  This is the name of the routine in question. It will be parsed out of the error string in .01. This will make the errors much easier to cluster around the causitive routine. This may actually be amended from the error
    string presentation if the causative program is found to be different.
3.1 APPLICATION 0;5 POINTER TO PACKAGE FILE (#9.4) PACKAGE(#9.4)

  • LAST EDITED:  MAR 05, 2008
  • DESCRIPTION:  This field will help to identify who are the responsible parties for this problem. Eventually, as a package is identified, the primaries and secondaries will be notified of the problem automatically as the problem
    happens.
  • TECHNICAL DESCR:  This is a pointer to the Package File. Each package should indicate a mail group that tracks the responsible parties for this specific package. This should include any IRM primary and secondary folks as well as any ADPAC
    personnel in the specific area of concern with this package.  The groups should be self-enrolling and be able to receive the generated email that will be batched for the errors of the day.
4 FREQUENCY 0;6 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>99999999)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  OCT 23, 2007
  • HELP-PROMPT:  Type a Number between 1 and 99999999, 0 Decimal Digits
  • DESCRIPTION:  
    This is the number of times that the error has been encountered, ever.  See FREQUENCY DISTRIBUTION below for how the error is occurring during the run of the day.
5 FREQUENCY DISTRIBUTION 4;0 Multiple #3.0775 3.0775

  • LAST EDITED:  OCT 23, 2007
6 LAST GLOBAL 3;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>240!($L(X)<2) X
  • LAST EDITED:  DEC 17, 1999
  • HELP-PROMPT:  Answer must be 2-240 characters in length.
  • DESCRIPTION:  
    This is the last global referenced with the first such error recorded.  If subsequent errors are recorded, and have different globals listed, they will be recorded in the following detail under ERROR EVENTS.
7 STACK LIST 6;E1,245 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>245!($L(X)<3) X
  • LAST EDITED:  OCT 31, 2007
  • HELP-PROMPT:  Answer must be 3-245 characters in length
  • DESCRIPTION:  
    This is generated from the GETSTK^XTERSUM function call.  It is the chain of calling levels which were accessed to bring about the error.
    WRITE AUTHORITY:  @
8 UPLOADED DATE/TIME 0;7 DATE

  • INPUT TRANSFORM:  S %DT="ESTX" D ^%DT S X=Y K:X<1 X
  • LAST EDITED:  APR 03, 2008
  • HELP-PROMPT:  (No range limit on date)
  • DESCRIPTION:  
    This field holds the date/time that the Error Summary was set to a consolidation site.  A message will be sent if this field in empty or less than the "Last seen" field.
10 ERROR EVENTS 1;0 Multiple #3.07701 3.07701

  • DESCRIPTION:  This is the $H date and the Sequence number of this error on that $H date. It provides an easy way to scan quickly historic occurrences of these errors. Long period failures will become more evident when they start
    showing up as reoccurring situations which will need to be dealt with.
  • TECHNICAL DESCR:  
    This will be pulled from the $H day subscript in ^%ZTER( and the sequence number which provides the error profile.  It will look like; 58054:3
20 LINE OF CODE 2;E1,245 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>245!($L(X)<3) X
  • LAST EDITED:  MAR 05, 2008
  • HELP-PROMPT:  Answer must be 3-245 characters in length
  • DESCRIPTION:  
    This is the original line of code which caused this problem.  It should be the same for all occurrences, but may reflect other failures on the same line.
    WRITE AUTHORITY:  @
30 DISCUSSION 30;0 WORD-PROCESSING #3.07702
31 SUPPORT PERSONNEL 31;0 POINTER Multiple #3.077031 3.077031

Found Entries, Total: 4

ERROR TEXT: H+13~XUSCLEAN, <WRITE>    ERROR TEXT: POST+3~BDW10P5, <SUBSCRIPT>    ERROR TEXT: RE+2~XMLTCP, <READ>    ERROR TEXT: SEND+4~XMLTCP, <WRITE>    
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointer To FileMan Files |  Fields |  Found Entries |  All