This document points out the key differences and similarities between the CA and CSI (BIM) FAQS (ASO & PCS) and GSS. For BIM-GSS, you will be executing CSIPKINT and BIM$INIT, followed by the BIM-FAQS/ASO and BIM-FAQS/PCS initialization: // SETPFIX LIMIT=4K (required if under VM) // EXEC CSIPKINT // EXEC BIM$INIT,SIZE=256K /* * ISSUE SET SDL FOR BIM$CGSV if using BIM$CGRX in dynamic ptn SET SDL BIM$CGSV,SVA /* * START FTL // EXEC GSFTL,SIZE=256K RDL=CREATE FAQS RDL=END /* // EXEC $FAQSHC6 CACHE=1M,PRELOAD=1000 /* * INITIALIZE GSFAQS // EXEC GSFAQS,SIZE=256K STARTUP FAQSASO /* * ISSUE SET SDL FOR $FAQSVM if using VMCF SET SDL $FAQSVM,SVA /* * STARTUP FAQS/PCS // EXEC JCLXCU,SIZE=JCLXCU ENABLE,LOAD=N,LOG=Y,DSN=Y,DSNLOG=Y,EVENTS=8000 /* The SETPFIX above is required only if you are running under VM and no ALLOCR value is specified for the BG partition. The GSFTL and GSFAQS execution JCL can be the same as you have currently. The "STARTUP FAQSASO" command for GSFAQS indicates to load the default entries that are distributed with the product, which we recommend for the initial start up of BIM-FAQS/ASO. Once you have the system and the on-line active, we highly recommend you create/use your own startup, message, and command members to match your environment. The FAQSASO message, command, and startup members are examples to get you started and to show some of the capabilities of automation. The definitions you were using can be backed up and restored using the FAQSUTIL utility program using the following process, or you could just back up and restore the CA-GSS MON and VIO PDS files to new CSI MON and VIO PDS files before installing BIM-GSS and BIM-FAQS 5.3A: You would create the following job streams to back up and restore the CA-FAQS/ASO "system" members. Each BACKUP request will create a file with an ending tape mark, so you can backup one or more member types on the same tape or disk area. Be sure to check the CA-FAQS/ASO User's guide for proper JCL set up. Run the following using the VSE system running CA-FAQS/ASO: /* BACKUP CA-FAQS security user files // EXEC FAQSUTIL,SIZE=FAQSUTIL BACKUP PW /* /* BACKUP CA-FAQS console PFkey files // EXEC FAQSUTIL,SIZE=FAQSUTIL BACKUP AOPFK /* /* BACKUP CA-FAQS console message definition files // EXEC FAQSUTIL,SIZE=FAQSUTIL BACKUP AOMSG /* /* BACKUP CA-FAQS console command definition files // EXEC FAQSUTIL,SIZE=FAQSUTIL BACKUP AOCMD /* /* BACKUP CA-FAQS GSFAQS start up files // EXEC FAQSUTIL,SIZE=FAQSUTIL BACKUP AOFST /* /* BACKUP CA-FAQS user terminal filter files // EXEC FAQSUTIL,SIZE=FAQSUTIL BACKUP AORTE /* /* BACKUP FAQS on-line command definition files // EXEC FAQSUTIL,SIZE=FAQSUTIL BACKUP AOFOC /* Then using the tape produced, you restore the file(s) in the same order using the VSE system running BIM-FAQS/ASO: /* RESTORE FAQS security user files // EXEC FAQSUTIL,SIZE=FAQSUTIL RESTORE PW /* /* RESTORE FAQS console PFkey files // EXEC FAQSUTIL,SIZE=FAQSUTIL RESTORE AOPFK /* /* RESTORE FAQS console message definition files // EXEC FAQSUTIL,SIZE=FAQSUTIL RESTORE AOMSG /* /* RESTORE FAQS console command definition files // EXEC FAQSUTIL,SIZE=FAQSUTIL RESTORE AOCMD /* /* RESTORE FAQS GSFAQS start up files // EXEC FAQSUTIL,SIZE=FAQSUTIL RESTORE AOFST /* /* RESTORE FAQS user terminal filter files // EXEC FAQSUTIL,SIZE=FAQSUTIL RESTORE AORTE /* /* RESTORE FAQS on-line command definition files // EXEC FAQSUTIL,SIZE=FAQSUTIL RESTORE AOFOC /* The above will move all CA-FAQS control members. If you want to only backup/restore specific member names, change the parameter to include an equal followed by the name to process: BACKUP AOCMD=MYFILE and you would then restore with the same name included: RESTORE AOCMD=MYFILE If you want to backup/restore several members of the same type, use separate executions of FAQSUTIL as in the following: // EXEC FAQSUTIL,SIZE=FAQSUTIL BACKUP AOMSG=MYFILE1 /* // EXEC FAQSUTIL,SIZE=FAQSUTIL BACKUP AOMSG=MYFILE2 /* and then make sure the restore JCL is in the same order as shown above: // EXEC FAQSUTIL,SIZE=FAQSUTIL RESTORE AOMSG=MYFILE1 /* // EXEC FAQSUTIL,SIZE=FAQSUTIL RESTORE AOMSG=MYFILE2 /* If you need to move your own IMODS, you will need to backup the CA-GSS MON PDS file and restore it to the BIM-GSS MON PDS file BEFORE installing BIM-GSS and BIM-FAQS (ASO & PCS) 5.3A. You may need to compile these IMODs manually if any problems are encountered. You may have already defined your own GSFAQS startup, message, and command files for CA-FAQS/ASO configuration. These members should run fine with BIM-FAQS/ASO with only one possible exception. GSFAQS will not properly initialize if your CA-FAQS/ASO startup file does not have any partitions/classes selected in the "Eoj Console Summary" area. The solution is to simply update the startup file using the "GSFAQS Startup Definition" panel to update the member(s) in question. To do this, from the BIM-FAQS/ASO command line enter the AO I.G shortcut command, select the entries you need to update by placing an X next to them and pressing the enter key. This will take you to the GSFAQS Startup Definition panel, where you can simply press PF5 to fix the members. Once this is complete, you can IPL your system after changing the GSFAQS STARTUP command to use the member you wish. -------------------------------------------------------------------------------- The main difference in the BIM-FAQS/ASO start up process is the addition of the execution of $FAQSHC6, which is the hard copy file cache. Here you will specify an amount of 31 bit SYSTEM GETVIS to be used to contain the most recent hard copy file messages. The archiving begins as soon as the $FAQSHC6 program is executed. You should base the allocation size on 8192 (8K) records per MEG. You can cache as many lines as you wish. You can also specify a PRELOAD value, which determines how many hard copy file records are pre-loaded into the cache area. This feature allows you to provide continuity between IPL's, and allow users to access hard copy file data without requiring the file to be read. You can PRELOAD up to 999,999 records, if you have a large enough cache area allocated (CACHE=nnnnK/M). The cache is wrap around, so once filled the oldest lines will be overlaid by new ones. The hard copy file cache feature makes hard copy file access and initial user logons very fast, and allows you to eliminate system overhead and DASD reads that would otherwise be required. -------------------------------------------------------------------------------- Besides initialization with start up JCL, you will need to start the on-line interface(s) which are fully explained in the manuals. One thing that will be different is the requirement for FAQXCONS to be executed. FAQXCONS is actually the master console controller for BIM-FAQS/ASO. It is a single program (the CA version runs several programs under the covers) that handles any console, hard copy, and EXPLAIN access required. This single program will need to be run in a separate partition with very high priority (dynamic partition is ok). The advantages of using a single program rather than multiple, and separating it out of FAQSMAIN and FAQSAO control are as follows: 1) One single master FAQS console, which reduces system overhead. 2) FAQSMAIN can be any priority depending on response time versus overhead requirements. 3) You can run multiple FAQSMAIN partitions, spreading the workload out across multiple partitions, if you wish. If you try to access any of the above functions when FAQXCONS is not running, you will receive: GFO434E VSE CONSOLE ERROR, RC=FF.00 until FAQXCONS has been started. -------------------------------------------------------------------------------- We recommend you run the batch and on-line partitions separately to provide the best on-line performance. The on-line partition would contain within it the following possible phases: 1) FAQSMAIN - BIM-FAQS/ASO on-line command processor 2) FAQSIUX - If under VM and using the IUCV on-line interface 3) FAQSVMX - If under VM and using the VMCF interface 4) BIM$TIDR - If using the CICS and/or VTAM/BTAM interfaces. This is the equivalent of DCMTDRIV and DCMOTDRV in CA-GSS Of course each of the above phases may be run in a separate partition, but be aware that does result in some XPCC overhead. If you decide to run them in the same partition, you can use BIM$UTTS to handle this just like you did for DCMTASK with CA: // EXEC BIM$UTTS,SIZE=FAQSIUX,PARM='FAQSIUX#BIM$TIDR#FAQSMAIN' if you are using the IUCV interface, FAQSIUX must be the main task, and so will be the first in the parameter list and the value for SIZE=. This is an IBM requirement for IUCV access. If not using IUCV or not under VM, the order of parameters does not matter significantly, but be aware the main task is always the lowest priority in any partition task list, and the last attached sub-task is the highest priority. We recommend FAQSMAIN be the last entry in the list. NOTE: If you plan to have on-line access to BIM-FAQS (ASO & PCS) and BIM-GSS via CICS, you must use BIM$TICI for your PCT and PPT definitions instead of DCMOCIXP as with CA-GSS. Check the BIM-GSS manuals for more information as well as the member BGCICSDF.txt in the FAQS53A folder. This member pertains to CICS/TS use, but you can also use it as a reference for CICS/VSE 2.3 definitions. The batch partition would consist of the following possible phases: 1) JCLSCHED - The BIM-FAQS/PCS job scheduler (BIM-FAQS/PCS users) 2) FAQSAO - The BIM-FAQS/ASO IMOD (REXX) processor 3) FAQSVSPO - The VTAM secondary operator for FAQSAO if you intend to use the VTAM() function within BIM-FAQS REXX IMODs. -------------------------------------------------------------------------------- In addition to the above programs, you may want to run BIM$CGRX, which is the on-line REXX processor for the BIM-GSS and/or BIM-FAQS HTML interface, as well as the cross partition REXX processor for batch, CICS, and Entree. See the BIM-GSS 5.3A cover letter for more information. If you plan on running BIM$CGRX in a dynamic partition, you will need the SET SDL entry for BIM$CGSV as provided above. NOTE: A conversion process is required to go from CA to BIM-FAQS/PCS. Consult the manuals and cover letters for BIM-FAQS/PCS for full details. Be aware that CA-FAQS/PCS 5.0 has changed the way the EVENT file is being handled. This has made the conversion process more difficult than it used to be. If you have your master EVENT file from prior to CA-FAQS/PCS 5.0, it is much easier to convert. If you have any questions, contact CSI BIM-FAQS/PCS support. The other PDS files (VIO, MON, ARC, EVT, LOG) are created by the installation process, and require a prefix of CSS$ instead of SYS$. This will separate any CA-GSS PDS file access from CSI's BIM-GSS PDS access. We have found this is necessary to prevent CA-GSS from causing chaining errors in our PDS files. Also be sure the standard labels for CSS$xxx PDS files contain the full extent information to avoid any problems with installation and utilization. Usually it is not necessary to have the full extent data, but it does avoid possible errors seen in the past. BIM-GSS and BIM-FAQS (ASO & PCS) 5.3A provide for interfacing to any CA (former LEGENT/GOAL) products you have that have been upgraded to CA versions 5.0 and above. If you wish to use these capabilities and you experience problems, contact CSI BIM-GSS support. NOTE: When using BIM-GSS and BIM-FAQS (ASO & PCS) 5.3A to access CA products, you MUST make sure any old CA product codes for CA-FAQS/PCS have been removed and an IPL performed. Otherwise you will receive ABENDs in the BIM-GSS phase, BIM$PV31, when attempting access. -------------------------------------------------------------------------------- BIM-GSS versus CA-GSS All names have been changed to BIM$xxxx from the CA-GSS names. This will affect users with startup of the VTAM interface, CICS interface, BIM-CPR, and the batch REXX processing. See the complete phase name change list below. Be sure to read the manuals carefully to determine where these changes will affect you. All names have changed, but the following list are the ones you are most likely to encounter: Old Name New Name Tranid Description GSSLUSRV BIM$GMSR GMF request server/processor GSSLUTAB BIM$GMPT GMF product identification table REXXBAT BIM$RXBA Batch REXX processing routine DCMINST BIM$UTIN Product installation routine DCMINSTV BIM$UTIV VSE version determination DCMOCIXP BIM$TICI BCIN Transaction interface routine DCMPLT BIM$UTCP Attach subtasks from PLT or a CICS transaction DCMTASK BIM$UTTS Subtask loading routine DCMTDRIV BIM$TIDR Interface to VTAM , BTAM, CICS, and XPCC FAQSCICE BIM$CPEN BCPE BIM-CPR termination routine FAQSCICI BIM$CPIN BCPI BIM-CPR initialization routine FAQSCICP BIM$CPPR BCPP BIM-CPR print handling routine FAQSCICQ BIM$CPPS BCPS BIM-CPR screen print handling routine FAQSCICT BIM$CPSD BCSD BIM-CPR Dispatcher for Screen print transactions FAQSCICW BIM$CPPD BCPD BIM-CPR Dispatcher of print transactions FAQSCIST BIM$CPTA BIM-CPR request dispatcher subtask FAQTCIXT BIM$CPEX BIM-CPR CICS global user exit GSPDSU BIM$PUTL PDS utility routine GSPDSVAE BIM$PV31 Main PDS request processor GSPDSVAM BIM$PV24 PDS 24-bit bridge to BIM$PV31 GSPRDLD BIM$INIT BIM-GSS Initialization and definition routine -------------------------------------------------------------------------------- We hope the above information will make your conversion process easier. For full information on the 5.3A release check the various sections of our web site, www.csi-international.com. NOTE: With the 5.3A release, you can now download both products directly rather than wait for tapes. The ZIP files containing the products and install text files are in the Downloads and Documentation area of our web site, www.csi-international.com. The files are BGSS53A.zip and BFAQS53A.zip. Be sure to read the install text files for both products. If you still need tapes, contact your sales rep to get what you need. Be sure to read the readme and READTHIS text files, as well as the other documents in the BIM-FAQS/ASO 5.3A support area of our web site for information and reference. If you have any questions, let us know by phone or via email at: support@csi-international.com. Welcome aboard!