M DECUS U. S. Chapter     SIGs Newsletter,   Volume  5, Number 3  November 1989 >                         Wombat Examiner,   Volume 11, Number 3    @ ----------------------------------------------------------------+                       From the Editor's Pen @ ----------------------------------------------------------------  A As you  are  heading  out  for  Anaheim  to  the  1989 Fall DECUS A Symposium, there  are  some  reminders  about  activities  at the % symposia and some late-breaking news:   A    o  Digital made  announcements  in  September  at  the time of A       European DECUS  and  early  in  October  in  the  US of new A       versions  of  DATATRIEVE  (and  a  lot  of  other  products A       including some very interesting  new  ones).  You will note A       the  announcements  which  follow  in  this  issue  of  the A       newsletter.   You  will  also  want  to  attend appropriate 8       presentations in Anaheim for detailed information.  A    o  In last months issue of  the newsletter a Special Rally PIR A       Ballot appeared.    Interest  in  Rally  is increasing very A       rapidly.  Now is the time to give feedback to Digital about A       future directions of  Rally.    The  deadline for receiving ;       your returned Rally PIR ballots in December 15, 1989.   A    o  Bernadette Reynolds, our  Symposium representative, reports A       that Working Groups meeting in Room 7 & 8 in the Convention A       Center have been moved  across  the street to the Palisades A       Room in the Hilton Hotel.    For the DTR/4GL SIG, this will A       affect  the  Oracle  Working  Group  meeting  scheduled for A       Tuesday,  12:00  to  1:00PM  which  will  now  meet  in the A       Palisades Room of the Hilton.   Other Working Groups should A       not be  affected,  but  you  should  check the Update.Daily 1       schedule for any other last-minute changes.   A    o  Those who wish to  volunteer  to  be  a Session Chair for a A       DTR/4GL SIG  sponsored  session  are  invited  to  attend a A       drop-in meeting at 5:00PM in  the  DTR/4GL SIG Suite in the A       Marriott Hotel on Sunday, November  5.   See the article by >       Harry Miller in last month's newsletter for the details.   See you in Anaheim.   :                                   Joe H. Gallagher, Editor  A -----------------------------------------------------------------   /                  Announcing VAX DATATRIEVE V5.0   >   John L. Henning, DTR/4GL SIG Digital Counterpart, Nashua, NH  A -----------------------------------------------------------------   A Digital  Equipment  Corporation   is   pleased  to  announce  VAX A DATATRIEVE V5.0.   This  article  reviews  the  two major feature A areas of the product  (support  for DECwindows and VAX CDD/Plus), 7 and acknowledges contribution by DECUS to this release.    The Wombat Does Windows   A VAX DATATRIEVE V5.0 takes advantage of several capabilities which @ are available on DECwindows workstations.  The product provides:  A     - Multiple  windows.    Windows  are  available  for  primary A       command input and results,  HELP,  Guide Mode, SHOW command "       output, and graphics output.  A     - Scroll bars.    You  can  move  horizontally and vertically 5       through output using the mouse and scroll bars.   A     - Pull-down menus.  Certain  commonly-used options can now be -       selected directly from pull-down menus.   A     - Screen resize.  You can use the mouse to expand or contract >       the primary display area, up to 51 lines by 124 columns.  A     - Dictionary navigation.  You  can  use the mouse to navigate A       through dictionaries, expanding and contracting directories .       to find and select contents of interest.  A It should be noted  that  although  you can select common options A from menus, the DATATRIEVE  language (commands and statements) is A still  available,  and  is   in   fact  required  for  most  data  manipulation commands.    # Support for CDO-Format Dictionaries   A VAX DATATRIEVE V5.0 allows  use  of  both older "DMU" (Dictionary A Management Utility)  dictionaries  and  the  newer  "CDO" (Common A Dictionary Operator) dictionaries.  DMU dictionary operations are A identified by pathnames (for example, CDD$TOP.DTR$USERS.OLIVOTTO) A and  CDO  dictionaries  are   identified  by  the  VMS  directory A specification  which  provides   the   dictionary's  anchor  (for > example, DISK3:[NINO]).  DTR V5's dictionary support includes:  A     - Read/write capability for  storing and accessing DATATRIEVE >       record and domain definitions in CDO format dictionaries  A     - Access to  CDO  field-level  definitions  for  inclusion in A       DATATRIEVE  record   definitions   stored   in  CDO  format        dictionaries  A     - Access  to  CDO  commands  to  perform  pieces-tracking  on        domains and records   A     - Use of search  list  logicals  that  let you treat multiple 2       physical dictionaries as a single dictionary  A     - Ability to ready a  CDD$DATABASE  object  that points to an 3       appropriate CDD$RMS_DATABASE object directly    A For this release of  DATATRIEVE,  we  have chosen to provide full A CDO support for the objects which  are most commonly used by both A DATATRIEVE and other applications,  such as RECORDS, DOMAINS, and A PORTS.    DATATRIEVE's   private   dictionary  objects  (such  as A PROCEDURES  and  TABLES)  continue  to  be  stored  in DMU-format  dictionaries only at this time.     ( Contribution by DECUS to DATATRIEVE V5.0  A Digital  thanks  the  DTR/4GL  SIG  for  their  contributions  to A Version 5.0.  The SIG  and  its leadership have provided numerous A requests for improvements  to  DATATRIEVE;  have  often served as A Field Test sites  for  the  product;  have  participated in early A Human Factors  testing;  and  had  very  direct  input  to recent A decisions regarding the  tuning  of  the  product  interface.  We A appreciate the SIG's contributions  and look forward to continued  partnership.  A VAX DATATRIEVE V5.0 will be on  the demo floor at Anaheim Fall 89 A DECUS Symposium, and two  sessions (on Monday afternoon, November A 6th)  will  be  devoted  to  in-depth  coverage  of  Version  5.0 	 features.     A -----------------------------------------------------------------   2               Announcing DATATRIEVE-11 Version 3.3;       Joe Mulvey, Digital Equipment Corporation, Nashua, NH   A -----------------------------------------------------------------   A DATATRIEVE-11 is an  interactive  query,  report-writing and data A maintenance system  designed  to  give non-computer professionals A easy access to system databases.    It has many on-line prompting A and help features to simplify the tasks of defining, managing and A retrieving data.   DATATRIEVE-11  is  especially useful for users A such  as  business  analysts  and  middle  management,  who  make A frequent and constantly  changing  requests  for data from large, A corporate databases.  It can  also  be used to build and maintain  small, personal databases.  A DATATRIEVE-11 V3.3  is  supported  on  the RSX-11M, RSX-11M-PLUS, A RSTS/E, Micro/RSX and  VAX-11  RSX  operating  systems; and under A VAX-11 RSX on the  VAX/VMS  operating  system.  All DATATRIEVE-11 A based products  provide  common  functionality  using  one set of / sources across all supported operating systems.   
 V3.3 FEATURES   A Some of the  key  enhancements  made  for  DATATRIEVE-11 V3.3 are A listed below.  For more complete product information please refer A to  the  appropriate  Software  Product  Description:  SPD  12.48 A (DATATRIEVE-11);  SPD  18.15  (Micro/RSX  DATATRIEVE-11);  or SPD  25.14 (PDP-11 DATATRIEVE/VAX).  A   * DATATRIEVE-11 provides  lexical  functions  consisting of the      following four groups:  %          Functions using numeric data *          Functions using alphanumeric data          Functions using dates(          Functions relating to processes  A   * DATATRIEVE-11 can now determine  at installation time whether A     or not floating point hardware is present.  If floating point A     hardware  is  present,  inline  floating  point  code  can beeA     excluded from the task  image  if  desired.  This feature, if A     used, provides  the  user  with  significant  additional pool-     space. -  A   * A new EDIT interface  to  EDT,  which  replaces QED, has beenr     added for easier editing.-  A   * Time capability  has  been  added  to  the  DATE datatype for A     better resolution of time.  Previously the resolution of timet      for DATATRIEVE-11 was a day.  A   * A new AUTOINSTAL based  feature  has  been added to allow for A     easier installation.    This  feature  will  be available on: %     RSX-11M, RSX-11M-PLUS and RSTS/E.   A   * A system default for  the initialization file (QUERY.INI) hasf     been added.   A   * DATATRIEVE-11 can now build  and  use  Supervisor Mode RMS on A     those processors where both the hardware and software support A     this feature.    This  feature  will  provide  the  user with &     significant additional pool space.  A   * Documentation has been completely  updated and repackaged.  ApA     new set of  documentation  will  accompany this release which A     will  provide  a   more   comprehensive   and   easy  to  uset     documentation set.  A   * This release provides  full  layered  product support for theoA     License  Management  Facility  (LMF)  (PDP-11  DATATRIEVE/VAXd
     only).  
 Support Plans   A A full range of Software  Product  Services is available.  Please A contact your  SPS  Business  Account  Specialist  for  a completetA description  of  support  plans  and  additional  information forDA Self-maintenance,   BASIC,   DECsupport,   Right-to-Copy  Update,m> Installation, Media Update, and Documentation Update services.  A -----------------------------------------------------------------e)                        Dear Wombat WizardeA -----------------------------------------------------------------r Dear Wombat Wizard:e  A Like most users, we use  a  combination of languages and tools tohA solve  our  computing  problems.      These  include  DCL,  third A generation languages, a word  processor, graphics and statisticaliA packages, and, of course,  a  lot  of  DATATRIEVE.  Our users areaA technical and profession people who are NOT computer experts.  WeeA try to make applications which are  easy to use and which require A an absolute minimum  of  keystrokes.    All  of the languages and-A tools we use except DATATRIEVE allow the entry of only a carriageRA return to indicate a default or null  entry.  Our users find it aaA real pain to have to enter  a  SPACE and a RETURN at a DATATRIEVE-? prompts when everything else allows the entry of just a RETURN.   A Why does DATATRIEVE required the  entry of at least one characteraA and  how  can   we   work   around   this  irritating  DATATRIEVEX
 restriction? n  )                                   Signed,r  A                                   Annoyed by an extract charactera  
 Dear Annoyed:c  A This is a really good  question.   So that all readers understandoA the  significance  of   the   question,  consider  the  followingl! apparently very simple situation:u   DTR> DECLARE FOO PIC X.e DTR> FOO = *."value of Foo"u Enter value of Foo: <CR> Enter value of Foo: <CR> Enter value of Foo: <CR> Enter value of Foo: <SPACE><CR>  DTR>  A DATATRIEVE (both VAX and  PDP-11)  will  not  accept the entry of A nothing, and will keep prompting until the user enters a SPACE orl; some other non-null character ahead of the carriage return.   A The Wizard consulted some  DATATRIEVE  developers and they statedsA that the reason why DATATRIEVE requires non-null input is that it A differentiates between the null string and the blank (all spaces)aA string.    While  in  most   cases  DATATRIEVE  could  make  some A reasonable assumptions about what  to  do  with null input, there A are some esoteric situations where a null string does not provide A DATATRIEVE with enough data  type  information to do a reasonable A conversion.  However, the  Wizard believes that the "restriction" A for non-null  input  arises  because  of  some  conditions in the A PDP-11 input/output routines;  DATATRIEVE  was originally written A for RSX.  In the  current  versions of DATATRIEVE-11, it is still A not possible to  use  a  null  string.    And this restriction in A DTR-11  has  been   perpetuated   in  VAX-DATATRIEVE  for  upward  compatibility. w  A I guess the "bad" news is  that's the way DATATRIEVE works and isIA likely to work from now on; the "good" news is that there are twopA work-arounds, which depending upon your mood, are relatively easym to do.  ? I will describe the first and give full details for the second.e  A If you use  a  3GL  front  end  to  callable  DATATRIEVE, you cannA control all terminal input - both commands and statements as welleA as data.  An example  of  this  is command line recall using SMG$aA calls as described  in  an  article  by  Dana Schwarts, Volume 2,yA Number 2, page DTR-3.  Your 3GL code could be modified to allow aa% null input and convert it to a blank.A  A The second work-around would  be  the  use  of a function such asoA FN$DTR_INPUT  to  accomplish  the  input.    I  have  written theeA function in FORTRAN because  FORTRAN  is the most widely licensedmA 3GL on Digital computers (and  because  that  is the 3GL that theOA Wizard  has),  but  in  this  case,  VAX-BASIC  would  be  a moreoA appropriate language because BASIC  allocates string variables inrA a way which  is  more  compatible  with  DATATRIEVE.  Anyway, thei function is:  B         INTEGER FUNCTION DTR_INPUT(PROMPT_MIDDLE, RETURNED_STRING)E !       An integer function which partially mimics DATATRIEVE input, d2 !       but which allows the input of just a <CR>.L         CHARACTER*(*) PROMPT_MIDDLE     ! the prompt between "Enter " & ": "C         CHARACTER*(*) RETURNED_STRING   ! the returned input stringiG         CHARACTER*140 PROMPT            ! allow for a big prompt stringrL         INTEGER STATUS                  ! the status returned from sys calls=         INTEGER*2 INPUT_CHAN            ! the channel for I/Or8         INTEGER CODE                    ! QIOW parameter;         INTEGER INPUT_BUFF_SIZE         ! input buffer sizeiG         INTEGER PROMPT_SIZE             ! the size of the prompt string-G         INTEGER INPUT_SIZE              ! actual length of input stringgB         PARAMETER (INPUT_BUFF_SIZE=255) ! this is too big, but ...         CHARACTER*255 INPUT-E         INCLUDE '($IODEF)'              ! get definitions for FORTRANE=         STRUCTURE /IOSTAT_BLOCK/        ! I/O block structuren?            INTEGER*2 IOSTAT, TERM_OFFSET, TERMINATOR, TERM_SIZEa         END STRUCTUREa:         RECORD /IOSTAT_BLOCK/ IOSB      ! actual I/O blockI         INTEGER*4 SYS$ASSIGN            ! system call to assign a channelIG         INTEGER*4 SYS$QIOW              ! system call to read with waitnK         INTEGER*4 SYS$DASSGN            ! system call to deassign a channelt !f" !       assign a channel to do I/O !e6         STATUS = SYS$ASSIGN('SYS$INPUT', INPUT_CHAN,,)8         IF (.NOT. STATUS) CALL LIB$SIGNAL (%VAL(STATUS)) ! % !       set code for read with prompti !/         CODE = IO$_READPROMPT  !s; !       determine the length of the prompt string passed ine ! D         STATUS = STR$TRIM(PROMPT_MIDDLE, PROMPT_MIDDLE, PROMPT_SIZE) ! < !       if string is too long, truncate it to 132 characters ! &         IF (PROMPT_SIZE .GT. 132) THEND             PROMPT_SIZE = 132           ! truncate to 132 if too big             END IF !aB !       prepend 'Enter ' and append ': ' to be compatible with DTR !n=         PROMPT = 'Enter '//PROMPT_MIDDLE(1:PROMPT_SIZE)//': 'R !EL !       increase size of prompt string by 8 characters (size of 'Enter'&': ' !i%         PROMPT_SIZE = PROMPT_SIZE + 8  !l !       do read with prompt  !n         STATUS = SYS$QIOW(, )         2               %VAL(INPUT_CHAN), $         2               %VAL (CODE),         2               IOSB,s         2               ,,$         2               %REF(INPUT),.         2               %VAL(INPUT_BUFF_SIZE),         2               ,,%         2               %REF(PROMPT),i*         2               %VAL(PROMPT_SIZE)) !   !       deassign the I/O channel !r-         STATUS = SYS$DASSGN(%VAL(INPUT_CHAN))g !iB !       return string; if too long it will be truncated to size of !       returned_stringE !h3         RETURNED_STRING = INPUT(1:IOSB.TERM_OFFSET)c !b< !       tell DTR of a successful completion of this function !r         DTR_INPUT = 1v         RETURN         ENDt  A Now to connect this function  to  DATATRIEVE, you need to add thet# following MACRO code to DTRFND.MAR:    ; FN$DTR_INPUT - . ; input is a stringl ; output is a string' $DTR$FUN_DEF FN$DTR_INPUT, DTR_INPUT, 2 (     $DTR$FUN_OUT_ARG TYPE = FUN$K_STATUSH     $DTR$FUN_IN_ARG  TYPE = FUN$K_DESC, DTYPE = DSC$K_DTYPE_T, ORDER = 1F     $DTR$FUN_IN_ARG  TYPE = FUN$K_TEXT, OUT_PUT = TRUE , ALL_LEN = 255     $DTR$FUN_NOOPTIMIZE  $DTR$FUN_END_DEF  A Then  compile  the  code,  add  it  to  the  library,  and relinkf DATATRIEVE something like:     $SET DEFAULT DTR$LIBRARY
 $MACRO DTRFNDd $FORTRAN DTR_INPUT) $LIBRARY/REPLACE DTRFUN DTRFND, DTR_INPUTa $@DTRBLD  A The function FN$DTR_INPUT can be  used  any place where one would 6 use the "*" to input data to DATATRIEVE.  For example:   declare choice_value pic 9.r< choice_value = fn$dtr_input("menu selection [default is 1]"), if (choice_value eq 0) then choice_value = 1  * Enter menu selection [default is 1] : <CR>  A So a null input can be used.   But the biggest advantage of usingcA FN$DTR_INPUT is that the prompt  can  be computed.  Currently one 8 cannot have a computed prompt in DATATRIEVE.  Consider:    DTR> ready yachts modify" DTR> for yachts modify using begin8 CON> price = fn$dtr_input("new price.  Old price is "| -# CON> format price using $$$,$$9.99)- CON> end  1 Enter new price.  Old price is $36,951.00 : 40000 1 Enter new price.  Old price is $17,900.00 : 20000-1 Enter new price.  Old price is $27,500.00 : 30000s ., .  .  DTR>  A This clearly has superior  capabilities  over the usual prompting.A in DATATRIEVE.  But if we  get something, we usually have to giverA something up.  We loose the  re-enter try when the input does noto7 satisfy the validation clause on the field.  Note that:i   declare price usage is reale edit-string is $$$,$$9.99 ( valid if price between 10000 and 20000 .! price = fn$dtr_input("new price")    Enter new price : 30000 ! Validation error for field PRICE.    print pricew     PRICEo  
 $30,000.00  A does not give a satisfactory result when the input is outside the A valid range.  But there  is  a  way  to work-around this as well.V Consider   declare price usage is realh edit-string is $$$,$$9.99 . ! price = fn$dtr_input("new price")n- while price not between 10000 and 20000 begin 5     print "Entered value not valid.  Please reenter."t%     price = fn$dtr_input("new price")      endi   Enter new price : 30000 ) Entered value not valid.  Please reenter.c Enter new price : 9000) Entered value not valid.  Please reenter.t Enter new price : 15000   A So a function like  FN$DTR_INPUT  can  be  very useful in certainpA situations, but it can not,  and  should  not, be used to do awayFA with the usual DATATRIEVE  prompted  input.   Such a function foroA input does bring up  some  other interesting possibilities.  With A very little effort it  would  be  possible to change DTR_INPUT bytA adding a second argument to do a read with a time-out.  One couldAA also change DTR_INPUT by adding a  second entry point or a second A argument which could be used for prompting with "Re-enter" rathereA than "Enter."  It would  even  be possible to change the functioniA to something like DTR_INPUT_VALIDATED in which the data type, andsA the upper and lower limit of valid input were passed, and the 3GLm' function would do the input validation.   A I hope you can put this function  to good use so your users won'tl" have to type any extra characters.  )                                   Signed,a  <                                   The Wombat Wizard (WEP&JG)  @ ----------------------------------------------------------------8                       Wombat Magic, Spring 1989 - Part 35 Session Co-Chairs: Dana Schwartz, DOD, Washington, DCvD                    Bert Roseberry, U. S. Coast Guard, Washington, DCI Session Editor:    Kyle R. West, Rally Editor, Teepak, Inc., Columbia, SC @ ----------------------------------------------------------------A Editors' note:  The  following  is  Part  3  of  a  highly editedfA transcription of the  Wombat  Magic  Session  at  the 1989 SpringhA DECUS Symposium in Atlanta,  Georgia,  which  occurred on May 11,lA 1989.    Part  2  appeared  in  the  September  1989  newsletter.uA Material which was  presented  on  transparencies has been mergedoA into the oral presentation.   An  attempt has been made to conveytA both the technical content of  the  Magic  Session as well as the A humor,  covert   intellectual   swaggering,   and   the  spiritedrA interchange of the presentations.   Material which appears in theiA text within square brackets [] has been added by the editor in aneA attempt to improve  the  understandability  of this very excitinghA Magic Session.  The material  presented  here is not presented inR- the same order as it occurred in the session.t    5 Lew Lasher, Digital Equipment Corporation, Nashua, NHa  A This is Rally magic  called  "Rally  Editing  Made Simple."  ThispA came to us because a customer requested it a couple of weeks ago. $ Fortunately, just in time for DECUS.  J +------------------------------------------------------------------------+J |   Problem: How to allow screen editing by the Rally illiterate user    |J +------------------------------------------------------------------------+  A The customer ask us  how  they  could  make  Rally easier to use, A imagine that, for some of their  users who are not enlightened inpA [the  Rally   definition   system].      The  customer  developediA applications that  worked  fine,  but  wanted  the  users  of thetA applications to be able to do some minor editing.  They wanted to A allow the end users just  to  change the appearance of the screenIA and not the functionality.   And  they said, 'Well, we don't wantrA to give them the  whole  Rally definition system, because they'llrA break  everything'.    Break   everything   in  their  shop  too.tA [Laughter] 'We just  wanted  to  permit  them  to  use the screeniA editor'.  And so we [DEC]  came  up with this solution here using(
 Rally macros.   J +------------------------------------------------------------------------+J | Solution:                                                              |J |                                                                        |J |       A. Define macros to get the user to and from the screen editor.  |J |                                                                        |J |          1. application form/report edit <RETURN>                      |J |          2. <FINISH ACTION> 2 <RETURN>                                 |J |          3. <FINISH ACTION> top <RETURN>                               |J |                                                                        |J |       B. Define a key definition file with a severely limited set of   |J |          commands.                                                     |J |                                                                        |J |          1. Exclude:  DO                                               |J |                       Menu Commands                                    |J |                       Finish Action                                    |J |                       Coordinates                                      |J |                       Insert Line                                      |J |                                                                        |J |          2. Include:  Macro 1,2,3                                      |J |                       Quit Application                                 |J |                                                                        |J |       C. Rally edit 'p1'/key=few_keys/macro=rally_made_simple          |J +------------------------------------------------------------------------+  A And basically you give people  macros  to  go just where you wantgA them to go in the Rally  definition  system.   So it is just likezA the shuttle buses here in Atlanta,  you  give people a way to get(A to the screen editor and a way to  get back.  So, I think it onlyoA takes 3 macros, as I have figured  it  out here.  One is that I'm A assuming that they get into Rally from DCL, that at the TOP leveltA of the definition system, this  [macro number 1] should get them,-A not to the screen editor, this  gets them to the point where they_A have to name what form/report  they  want  to edit.  Then it well A ask which form/report that they  want  to  edit and then they can1A type that in [or select the  F/R  from the LOV].  After they have=A typed in the form/report they  want  to edit then do macro numbertA 2, which flags  that  form/report.    After  putting the number 2tA there I realized that this is  bad  style, I should have used theDA key word, but I guess the work is done, and I can't remember whathA the key word is -- screen or  edit [screen is correct].  So I hadsA a 50/50 chance, I chickened out and just used the number 2.  ThatiA gets them to the screen editor.  Then give them a way to get out.uA And this [macro number 3] will  do it here, just FINISH ACTION toeA get out of the editor and that brings them back to the menu where A they edited the form/report.    And  TOP  will bring them back topA where they started.  This  is  multi-part, this is part A, giving A them macros to go where they  should  go.  In the next step [partcA B], we will prevent them from  going  anywhere else.  And the waypA you prevent  them  from  going  anywhere  else  is  using the keyeA definition facility in  Rally.    Because  you  can't go anywherelA without keys.  And so  you  define  a key definition file and you5A can do this by starting  with  your  favorite set of keys, EDT orbA WPS whichever, you edit  everything  out  of  it to remove nearlysA every command.  You get rid of the DO key and you want to get rid-A of all of the menu commands.    You know you may not realize, butnA when you run a  Rally  menu,  like  you  move  the cursor up to anA choice or down to a choice those are actually name commands, that A you can read all about  in  the Rally Command Reference Manual ifeA you have nothing better to do with your time.  And there is also, A even pressing <RETURN> on  a  menu,  like typing something in and A then pressing <RETURN>, that <RETURN>  is  a command that you can A define another key for or chuck from the key definition file.  So A if you get rid of that then people can still type on the menu but0A they won't be able  to  execute  anything  on the menu except thenA things you've defined to them,  which  is macros.  And let's see,eA I'm not sure about this, but  I  think  you'll want to get rid of A FINISH ACTION.  I am not sure  about that but what the hick, lets A get rid of it  too.    I  think  QUIT  ACTION is safe, but FINISHrA ACTION looks dangerous.  And that thing in the form/report editor,A to bring up the coordinates  screen,  that  is the GOLD A, you'll A want  to  get  rid  of  that  because  somebody  could  define anpA integrity error, we didn't  want  that  to  happen.   And I think A there is a command called INSERT  LINE and that is when you presstA carriage return  in  the  screen  editor.    Never press carriagerA return in the screen editor unless you're a Rally sophistic.  AndtA you do want to include a  few  keys  for  the users to be able to A use, one is to include  keys  for  the  3 macros you so carefullyhA defined.  And you have to give  people  a way out.  I am not sure A you might be able to get away  with giving them QUIT ACTION -- oh A I know why  you  don't  want  to  include  FINISH  ACTION or QUITaA ACTION, I knew there was a reason  for this, it all comes back to A me.  If  you  include  FINISH  ACTION  or  QUIT  ACTION then whenWA they're in the screen editor they  can exit from it, and get back-A some level of main use  and  may  press  one of your macros, thateA will work from some  bizarre  place  in  some wrong menu, and God A knows what it will do.   So  take  out FINISH ACTION and take outtA QUIT ACTION, but you got to  give  them  some way to go out.  You-A can give them QUIT APPLICATION  and  that  will take them all therA way out in case they  do  define  an integrity error, that alwayscA gets you all the way out,  works  just  as  will as CONTROL Y.  A A little slow but more elegant.    And  I think that's it for keys. A Oh by the way, I guess I should mention that when you're definingiA the macros you should use the real set of keys, because otherwisetA your typing would return and won't  do anything.  That's why thattA is step A and this  is  step  B,  it's sequential.  And after you,A have done that, then you  just  give  people some kind of captivecA command procedure, that lets  them  edit  their desired file withwA these keys and with those  macros.    And there you are Rally forp the illiterate.     A B. Paul Bushueff, DOT Transportation System Center, Cambridge, MAl  A [Paul's magic is titled "Handling a  Long LOV in Rally."]  We had A a problem about 3 or 4 months ago when we had to show to a user asA long LOV list.  That long  LOV consisted of a sequence number andlA a description of that number.   The problem is the way that Rallyw? works, you can only start at the beginning and page to the end.-  I +-----------------------------------------------------------------------+wI |                             RALLY                                     |-I |      o  Long LOV                                                      |aI |-----------------------------------------------------------------------|eI |         Number                              Description               |sI |         ------                              -----------               | I |          20                                 Galley                    |iI |          201                                Galley Store              |fI |          202                                Galley Sink               |wI |          21                                 Bridge                    |rI |           .                                   .                       |]I |           .                                   .                       |wI |           .                                   .                       |-I +-----------------------------------------------------------------------+i  A Here we have a  LOV  of  about  800  to  1000 elements.  For some A people who know the  approximate  number  or know that it started A with a series of 20  or  30  or  something like that or they knoweA that it had to  do  with  a  certain description group, we really A wanted to be  able  to  search  them  [the  elements  of the LOV]EA numerical or alphabetical and be about  to start at a given pointR in the list.  I +-----------------------------------------------------------------------+ I |      o  Need to enter proper number.                                  | I |                                                                       |lI |         - Some know the approximate number                            | I |         - Some know the description                                   | I +-----------------------------------------------------------------------+   A The solution that we  came  up  with  was  that the user would be A allowed to enter on the  form  either a numeric starting point or - put an asterisk and any number of characters.   I +-----------------------------------------------------------------------+ I |         Solution                                                      | I |-----------------------------------------------------------------------| I |      o  Enter Starting Value                                          | I |                                                                       | I |         20                                                            |lI |              or                                                       |-I |         *GA                                                           |lI +-----------------------------------------------------------------------+aI |      o  Disable Rally LOV validation                                  |tI |      o  Use local function key                                        |gI |                                                                       |hI |         ADL                                                           | I |        -----                                                          | I |         - put number in a global variable                             | I |           use parameterized RSE (>=)                                  |cI |           call conditional LOV                                        |rI |                                                                       |tI |         - if *ab                                                      |rI |            put letters in global variable                             |lI |            use alternate RSE                                          |aI +-----------------------------------------------------------------------+   A Then we made sure that  the  LOV validation is disabled in Rally,2A using a local function key,  the  ADL  code at the local functiongA site.  If a number  is  entered  it  would  store the number in aCA global variable, use  the  parameter  RSE  and  use the >= searchnA criteria.  Then call the conditional LOV and what it would return A would be a  LOV  starting  with  the  numeric  field  that we had,A entered.  The alternative is that  if  you put in an asterisk, iteA would recognize  the  asterisk  as  character  and  it would work A exactly the same  way,  it  would  put  the alphabetic characters A following it in the global variable.   Use an alternative RSE anda# it would return an alphabetic list.     : John L. Henning, Digital Equipment Corporation, Nashua, NH  A [John's magic is titled "Goof  Proof  Rdb  for RALLY."]  This oneeA may not be all  that  magical  but  it  is  a really problem thati arises.D  J +------------------------------------------------------------------------+J |  Assumption:  RALLY/COBOL/DTR  application updates a database with     |J |               local validation - e.g. change salary for employee with  |J |               employee.dept = current user's dept.                     |J +------------------------------------------------------------------------+  A Assume that you have an  application  that is written in Rally ornA COBOL or DATATRIEVE.  Something where you get some fairly carefulhA structure put in place.  So that it will do exactly what you wantrA it to do.  Doing some validation  which might be done at the timebA of the application, based on  something that is determined there,vA at that time.  For  example,  you might have an application whicheA changes a salary for an employee, that you want to check that theOA employee department is  equal  to  the  department of the currentiA user or you might check that the person is actually authorized tos  make changes to that department.  J +------------------------------------------------------------------------+J |  Problem:  What if user comes in with Teamdata, DATATRIEVE or RDO and  |J |            does [his] own updates ??                                   |J +------------------------------------------------------------------------+  A The problem arises with what  if  somebody instead of running the A application that you so carefully  built, comes in with Teamdata,oA DATATRIEVE or RDO.    I  am  motivated  to  write this, simply inoA response to Bert's claim  that  [his]  would be the only Teamdata A magic.  This  is  actually  a  general  problem more general thanaA Teamdata but he might  be  coming  in  through Teamdata after youoA have so carefully setup the  [Rally] application to limit what hew can do.s  J +------------------------------------------------------------------------+J |  Solution:                                                             |J |            - Captive account "UPDATER"                                 |J |            - RDO ACL UPDATER "read+write+delete..."                    |J |            - In application login [login.com] define user              |J |              SYS$REMOTE_NODE  SYS$REMOTE_USER and check it in the      |J |              application                                               |J |            - RDO ACL * "read"                                          |J +------------------------------------------------------------------------+  A The solution is fairly sample.   You create a captive account you A might call it "UPDATER".  Then  in  RDO  you give it the ACL thateA only "UPDATER" has "read+write+delete...".  In the login.com filenA for the captive  account,  it  turns  out  that  you can define a,A logical name which picks up the remote user and remote node.  You A check against that in the application.  Then finally there is onehA last piece, what do you do  with all Teamdata or DATATRIEVE usersoA that you do want to allow to do reporting against this.  You giveu& them an ACL for read only.  That's it.    1                part 4 of Spring 1989 Wombat Magic "                                and8         the Author, Title, and Keywork Index to Volume 4  +                      will appear next montho  