PróM1ii [Internal Document] 2024 Guidelines best ideas Finish what you start. There is some value in putting 90% of the effort into 200 things. However, none of the value is realized with you don't finish them. Dedicate some time to finish items. Adding things to dev Can't add anything to Dev without 1) A reason why we added it and what we want to accomplish. 2) Test case or details. We need to get back to the problem quickly in the future. Not spend time wondering what the issue is. 3) We should likely always have a CSR immediately to collect progress notes, attach documents, and keep any details. None of this haprens in a program, just because it is in dev. *IC4t$-rbW.4 0pJ c:\Users\jtillia\Documents\2024 Guidelines.docx Page 1 [09/23/091
+ Fix data I, Other data not identified still exist + Corrective Action Mistake Proof Problem Containment Fix this data Preventative Action Follow up - Audit Escape Event [INTl Event is reported An Escape Event is a problem reported by our customer. EVENT_MAINT A single sentence should define the problem and attempt to explain it.Problem Statement Collect data and back it up Develop Cause Chain Duplicating the problem is paramount in resolving the problem. Collect any data the might point to issue and for analysis Use Fishone Diagram Ask "why" until the questions get stupid and don't move towards a root cause Root Cause Pr vafr1 Define what steps are requied to contain the problem. How to fix the data sn confirm the containment. How to prevent the problem from recurring. This is typically process corrections. Corrective action to resolve this event Always ask "can we mistake proof" this process. Set a date(s) to review any preventative actions taken and confirm this event has not recurred. • GOAL. Data fixed and problem will not happen in the future Escape_Event_Flowchart.vsdx Revision: 12/31/2024 Page: 1
The Command Editor The command line editor allows editing of a command line. It is of use in correcting typing errors or repeating saved commands, possibly after modihcation. The command The editor handles the following keystrokes: Ctrl-A or HOME Move cursor to start of command. Ctrl-B or Cursor Left Move cursor left one place. Ctrl-D or DELETE Delete character under cursor. Ctrl-E or END Move cursor to end of command. Ctrl-F or Cursor Right Move cursor right one place. Ctrl-G Exit from the command stack and return to a clear command line. Ctrl-K Delete all to the right of the cursor. Ctrl-L Convert command to lowercase. Ctrl-N or Cursor Down Display next command from command stack. Ctr-O or Insert Toggle insert/overlay mode. Ctrl-P Display 'previous command from command stack. Ctrl-R Search back up the command stack for a given string. The string may he entered either before or after the Ctrl- R. Using Ctrl-R again, finds the next item matching the supplied string. The search is case insensitive. Ctrl-T Interchange characters before cursor. Ct ri-U Convert command to uppercase. CtrI-W Amend casing of the "word' at or preceding the cursor position, cycling through uppercase, lowercase and title case. Ctrl-Z or Cursor Up Display "previous' command from command stack. Backspace Backspace one place. :2O2mi P.ket dt,'L, Ini.i,II iddm. O - QNA M,),i '11
Entering a command line contairing only a question mark shows a summary of the command editor keys. Command Editor Options The command stack editor operations are controlled by option codes which may be entered in field 3 of the $RELEASE VOC entry. These are: E Position the cursor at the end of a recalled command rather than the start. L Use the screen size to determine the default number of items shown by .L 0 Start in overlay mode. S Show the stack commands when moving back through the stack. x Clear the recalled command if the first character typed is not a control code. This mode cannot be used with E. Related concepts The Command Environment The Command Stack The VOC Pihe 5 2025 Rocket S)ftw.ir, I nr. /ii P.ght Rerci I Oper.O5i Sri rr M,nrri V
rnst.Jis 1,pfJ>. er.d eise mst e n ci S INDEX( string, substring {, occurrence}) IF index(wo.approved.iogons, u.user, 1) THEN wo.adrnin.fiag = END ELSE wo.acimin.fiag = U END LOCATE( string, dyn.array, field {, value subvalue }}{; order}) where string evaluates to the item to be located. dyn.array is the dynamic array in which searching is to occur. field is the field at which searching is to commence. value is the value at which searching is to commence. If omitted or zero, searching occurs at the field level. subvalue is the subvalue at which searching is to commence. If omitted or zero, searching occurs at the value level. order evaluates to the ordering string as described below. If omitted, no ordering is assumed.
Sou rce.control. rev Id = bp.gu i.qm *cash_su b <1> cur live Rev Nbr <2> current location <3> dev rev nbr <4> test rev nbr <5> live rev nbr <6> rel to live date Sou rcecontrolfile id=bp.gu i.qm *cash_su b*1 <1> dev date <2> test date <3> live date <4> revised by <5>rev comment <9> dependencies <10> csr nbr S.VD, OZDb! Pb 4-Th - - Po ( LtJIA P4r (Lvijao) 'J'i SA-LL iJS pa.. r t4