Screen Demon Revision 3.52.01 Release Notice Copyright (C) 1988 - 1993, Threshold, Inc. All Rights Reserved Contents I. Environment II. Installation III. Enhancements IV. Corrections V. Notes and Warnings I. Environment Operating system: AOS/VS 7.56 or greater AOS/VS II 2.01 or greater (requires patch number 83 for 2.01) Host language: AOS/VS Interactive COBOL 1.40 - 1.71 AOS/VS COBOL 3.20 - 3.71 AOS/VS C 4.00 Other languages to be determined II. Installation 1. Screen Demon requires a directory accessible via the pathname :SCREEN_DEMON_3.52 This can be a link if you do not want to actually load Screen Demon into your root directory. It is recommended that this release be kept separate from any previous version of Screen Demon. Rev 3.52 Screen Demon programs can be run simultaneously with programs using previous versions of Screen Demon. Note that this directory pathname differs from that expected by previous revisions of Screen Demon, where the directory was located in :UTIL. 2. DIR into the above directory. 3. Load the release tape, using one of the following commands, depending on the release media: 1600 bpi 9-track tape: LOAD/V/BUFFERSIZE=8192/DELETE :(0,1) 22-meg MV/2000 cartridge tape: LOAD/V/BUFFERSIZE=16384/DELETE :(0,1) QIC tape: TAR_VS/XTRACT/FILE=:0 LOAD/V/DELETE SD352(,U).DMP DELETE/V SD352<,U>.DMP 4. Install any update patch files loaded from tape file 1 using the command APPLY_SD_UPDATE This will also create the required subdirectory structure within the Screen Demon directory. 5. Revision 3.52 uses the same format for the SCREEN_DEMON.CONTYPES file as rev 3.00.03, so you should copy your existing version of this file to 2 the new directory. Also, the SD_TERMCAPS.SR file is similar, but new entries have been added. If you have customized the rev 3.00.03 version of this file, you should merge your changes into the new version. Then execute MAKE_SCREEN_DEMON.VM to create a new Screen Demon VM file for use by rev 3.52 programs. Alternatively, you can create a link in the new directory for the file SCREEN_DEMON_3.00.VM to point to the file of the same name in the :UTIL:SCREEN_DEMON_3.00 directory. The two revisions can share this VM file without problems, which will allow SD_SPY to see programs running both versions. This eliminates the need to convert all programs to the new revision at one time. 6. Revision 3.52 will use the same registration file as Screen Demon rev 3.00.03. You will need to create a link in the new :SCREEN_DEMON_3.52 directory for the file SCREEN_DEMON_REGISTRATION_3.00 to point to the file of the same name in the :UTIL:SCREEN_DEMON_3.00 directory. Alternatively, you may use the "Move Registration" option of the revision 3.00 SD_REGISTER program to move this file to the new directory. In this case, if you plan to continue running revision 3.00 programs, you will need to create a link for the registration file in the old Screen Demon directory pointing to the file in the revision 3.52 directory. You may also temporarily register the new version independently using the key code supplied on the last page of this release notice. 7. If you plan to use the Screen Demon mail system, you should either create a new Post Office directory using the SD_INIT_MAIL.CLI macro, or create a link in new Screen Demon directory pointing to the Post Office directory in the rev 3.00.03 Screen Demon directory: DIR :SCREEN_DEMON_3.52 3 C R E A T E / L I N K S D _ P O S T _ O F F I C E :UTIL:SCREEN_DEMON_3.00:SD_POST_OFFICE The link will allow programs using the two different revisions ofScreen Demon to exchangemail. 8. The configuration file format is basically the same as that of revision 3.00.03, but contains additional options. Rev 3.52 will accept configuration files created with rev 3.00.03, using default values for the new options not present in the older files. It is not necessary to modify or rebuild these files (using MAKE_SD_CONFIG.CLI). However, in order to use the new options, you will need to update your configuration files. Do this by following the instructions in the text file SD_CONFIG_UPDATE.DOC which contains the new options and directions where they should be inserted in an older configuration file. 9. If you were using the Printer Switcher in rev 3.00.03, the format of the SD_PRISWI_CONFIG.SR file in rev 3.52 is the same, but with additional options. You can use your existing SD_PRISWI_CONFIG files, or look at the rev 3.52 version to see the two new options. The USER command allows printer assignments by username, rather than console number. Support for pass- through printers attached to user terminals is now available using the PASSTHRU printer type. 4 10. If you have customized any of the following files in rev 3.00.03 Screen Demon, you should merge your changes into the rev 3.52 versions of these files: MAKE_PRISWI_CONFIG.CLI MAKE_SD_PLAY.CLI MAKE_SCREEN_DEMON.SL.C MAKE_SD_SPY.CLI LI MAKE_SD_SWAT.CLI MAKE_SCREEN_DEMON.VM.C NAMTB.SR LI PLAY.CLI MAKE_SD_CALL.CLI SD_CCL.CLI MAKE_SD_CONFIG.CLI SD_CLINK.CLI MAKE_SD_GATES.CLI SD_INIT_MAIL.CLI MAKE_SD_HKD.CLI SD_POSSESS.CLI MAKE_SD_ICDEB.CLI SDCALCULATOR.CO MAKE_SD_ICX.CLI SDCALENDAR.CO MAKE_SD_ICX_CONFIG.CLI SPY.CLI MAKE_SD_ICX_NAMTB.CLI MAKE_SD_INNER_RING.CLI 11. Link rev 3.52 Screen Demon with your programs the same way as with the previous revision. For Interactive COBOL, the MAKE_SD_ICX.CLI macro is used as before. Also, when building inner ring programs and shared libraries, the MAKE_SD_INNER_RING.CLI and MAKE_SCREEN_DEMON.SL.CLI macros function the same as in rev 3.00.03. Do not attempt to use patches from the earlier version with rev 3.52. 12. The rev 3.52 Screen Demon shared library is downward compatible with the ones in previous revisions, including rev 2.01.05. Programs linked or possessed to use the rev 2.01.05 or rev 3.00.03 shared libraries do not need to be re-compiled, re- linked, or re-possessed in order to use the rev 3.52 shared library. You may wish to run the MAKE_SCREEN_DEMON.SL.CLI macro to create a customized version of the rev 3.52 shared library. Then, arrange for your programs to find the new SCREEN_DEMON.SL instead of the older version. 13. Rev 3.52 Screen Demon inner ring programs are downward compatible with those created by rev 3.00.03. Programs linked or possessed to use inner ring programs do not need to be re-compiled, re- linked, or re-possessed in order to use rev 3.52 inner rings. You may wish to run the MAKE_SD_INNER_RING.CLI macro to create a customized rev 3.52 inner ring; the only one included on the 5 release tape is SCREEN_DEMON_RING_6.PR. Then, arrange for your programs to find the new inner ring programs instead of the older versions. There is one exception to the "no re-linking or re- possessing" rule. If you will be including the CEO or WordPerfect Office interfaces in an inner ring program (not possible in rev 3.00.03), you will need to re-link or re-possess programs that will use the inner ring so that they will contain the new ring 7 bootstrap code. This is necessary for these interfaces to successfully communicate with CEO_CP or the WordPerfect Office shell from the inner ring. III. Enhancements A complete list of enhancements can be found in the text file SD_3.52.01_ENHANCEMENTS.DOC IV. Corrections All known problems have been fixed, except for those listed in the "Notes and Warnings" section below. A complete list of corrections can be found in the text file SD_3.52.01_FIXES.DOC V. Notes and Warnings 1. There is an annoyance with the input of fields longer than the width of the screen on the last line of the screen, such as when entering a command line in CLI. While in insert mode via ^E, at the point when inserted characters would extend the end of the line (including any hidden characters accessible via ^A but not initially displayed) up to the right margin, the terminal will beep and it will no longer be in insert mode. 2. Field-oriented inputs that begin beyond column 80 may actually occur at column (col - 80). 6 3. Newer versions of VS/COBOL remember the console timeout setting from the most recent ACCEPT, and will not issue system calls to reset it if the setting is already thought to be correct. This can cause problems if a VS/COBOL subprogram is called from a hot key, since the COBOL runtimes do not expect multiple ACCEPT's to be active at the same time. If an ACCEPT in a hot key routine has a timeout, but the ACCEPT where the hot key was pressed does not, then pressing the hot key twice at the same ACCEPT will result in the hot key subprogram's ACCEPT occurring without a timeout the second time. Work-around patches for various revisions of VS/COBOL can be obtained from Threshold if this is a problem for your system. 4. Screen Demon does not support the "Selected Field Translation" option of the ?WRITE system call. The only program this seems to affect is DISPLAY.PR. 5. Screen Demon does not support the undocumented "Edit Read" subpacket of the ?READ system call. The only programs known to use this option are CEOWRITE.PR and CEO_WP.PR. 6. SD_PLAY cannot properly play a console log file backward if it contains D400 hardware window or margin commands. 7. SD_SPY only shows 80 columns even if the remote process being viewed has the screen in D400 compress mode. 8. Because of the design of the ICOBOL revision 1.70 and 1.71 interpreter, it is not possible to invoke an ICOBOL program via a Screen Demon hot key from an input occurring as a result of an assembler call from an ICOBOL program. For example, the Screen Demon Calculator program, which is written in ICOBOL, uses the SD_READ_CHAR call to input characters from the keyboard, rather than using an ACCEPT statement. If a hot key is pressed that is assigned to another ICOBOL program, such as the Screen Demon Calendar program, it will be ignored. Any other type of hot key will execute normally. 9. There is a problem with console interrupt handling in ICOBOL revisions 1.70 and 1.71 that occasionally causes the interpreter to panic or hang when ^C^A or ^C^B is pressed. This is not a Screen Demon problem, since it will also occur with the standard ICX when ^C or ^\ is pressed. However, because of 7 the potential for ISAM file corruption, you may wish to set the Screen Demon configuration file option IGNORE_CONSOLE_INTERRUPTS? to YES. Note that the ICX switches /NOINT and /NOQUIT will not help! 10. A problem in AOS/VS revision 7.70 affects Remote Input in SD_SPY. If you go into Remote Input mode for a particular console, and then leave Remote Input mode, it will be impossible for any Spy process to go back into Remote Input mode for that console until the process that was running on that console terminates. The error message will be "Remote PID Already Controlled By PID 0". This problem is fixed by patch # 38 for AOS/VS 7.70, which is available from Data General. 11. Because of an incompatibility with the current revision of AOS/VS COBOL (rev 3.71), the default value for the Screen Demon configuration file option TRIM_SPACE_UNDERSCORE_ON_INPUT? has been changed to NO; it was set to YES in earlier revisions of Screen Demon. If you are using VS/COBOL revision 3.70 or above, or revision 3.20 or earlier, this question must be answered NO; otherwise, function keys may not be accepted properly. However, if you are running anything else, you will probably want to set this option to YES. See the Configuration File chapter in the Developer's Guide for more information. 12. There is an error in the definition of the D470C terminal in the SD_TERMCAPS.SR file. The model id code is specified as 54; it should be 44. After making this change, execute the macro MAKE_SCREEN_DEMON.VM.CLI to rebuild the Screen Demon VM file so that it contains the proper termcaps table. 8