A FCS RESIDENT LIBRARY FOR RSX11M V3.2 FCSRES.TSK is a working FCS resident library for use on an RSX11M V3.2 system. All standard DEC utilities(except the RMS ones) can be built with it to provide both an in-core size saving and a on-disk size saving. The savings vary from task to task but usually is around 2K per task although the exact savings varies widely. FCSRES.CMD will build FCSRES.TSK and FCSRES.STB and auto-ZAP its PSECT. The following things should be kept in mind. All of FCS can no longer fit in the library. The changes to OPEN midway through V3.1 forced the old FCSRES.MAC to build a larger than 4K task. Some less used items have been removed. But fear not. The trick published in the software dis- patch of building the library, and then ZAPPING it's psect works like a charm. Once the psect is ZAPPED, no nasty taskbuilder error mes- sages will appear, and all the utilites work with breathtaking speed(at least faster) which is possible when FCS overlays don't have to be called in. The difference in loading one one's system disk is very dramatic particularly when used with the new large F11ACP or the PLAS F11ACP. In all fairness I should point out that after the October Software Dispatch SLP patches are applied, the DEC FCSRES.MAC will probably work. The DEC maintainer feels that by including global references to ARITH and DARITH that all taskbuilding problems are re- solved. I am not quite so sure. I seem to recall (back when I was trying to find ways of building everything with FCSRES) that there may be a few things left which still won't build. In time I will go back and try rebuilding everything with a new FCSRES and see if DEC is right. For the present, ZAPPING the PSECT is foolproof and will in- sure that absolutely everything builds. Substantial system benifits result in building the utilities with an FCS resident library. Although none of the tasks decrease in size by anywhere close to 4K(they are overlaid to the teeth), they no longer have to bring in overlays as they execute (or at least not the FCS ones). This means that the total demand placed on the system disk goes down abruptly. Additionally, some tasks decrease dramaticaly in size. The new print spooler tasks, and COT are HUGE without building with FCSRES. Before building them with FCSRES I was not sure I was going to be able to use them on our system. They sit in core all the time (stopped) and will checkpoint out when another task comes in, but they represented a lot of code to be constantly checkpointing in and out. Built with FCSRES, they are small, checkpoint quickly and not as often because they don't fragment core as badly(we only have a 124 K machine). The command file, FCSRES.CMD will build a working FCSRES.MAC and automatically ZAP its PSECT. However, for the more adventurous of you, I am including a tantalizing alternate FCSRES version. This will support ANSI magtape(and BIG BUFFERING). I must point out that I have not had the opportunity yet to build all tasks on my system with this version, but I expect to do so soon so that I can take advantage of PAGE 2 the big buffering in the present FCS. In fairness I must admit that I did not create this version. It was passed on to me by James Kirkman. For those with tighter core requirements, an ANSI FCSRES is provided which maps all the OPEN routines into one routine thereby saving enough space to insert the ANSI code. Richard Kirkman states that he has been using it with success on his system for a month or so. If it works for him, it is probably very solid.