APAR status
INTRAN
Error description
*************************************************************** * INFORMATION ON RUNNING IBM FINANCIAL BRANCH SYSTEM SERVICES * * VERSION 3 (FBSS (DOS)) UNDER MICROSOFT WINDOWS 3.0 * * AND IBM WINDOWS CONNECTION, IF MICROSOFT WINDOWS * * COMPATIBILITY IS ANNOUNCED IN YOUR COUNTRY. * *************************************************************** THE FOLLOWING INFORMATION CONTAINS TWO PARTS: - COMPATIBILITY BETWEEN FBSS (DOS) AND MICROSOFT WINDOWS, AND - COMPATIBILITY BETWEEN FBSS (DOS) AND IBM WINDOWS CONNECTION. FBSS (DOS) AND MICROSOFT WINDOWS IN 386 ENHANCED MODE IBM FBSS (DOS) WITH MICROSOFT WINDOWS RUNNING IN 386 ENHANCED MODE PROVIDES: - MEMORY RELIEF IN DOS ENVIRONMENT - ALTERNATIVE USAGE OF A FBSS NON-WINDOWS APPLICATION PROGRAM AND OTHER WINDOWS OR NON-WINDOWS APPLICATION PROGRAMS UNDER SOME KIND OF NAVIGATOR INTERFACE. HARDWARE REQUIREMENTS --------------------- TO RUN FBSS (DOS) WITH MICROSOFT WINDOWS, YOU NEED AN IBM PERSONAL SYSTEM/2 WITH THE INTEL 80386 PROCESSOR (OR HIGHER), AND 2MB (OR MORE) OF MEMORY (640KB OF CONVENTIONAL MEMORY AND 1024KB OF EXTENDED MEMORY). STARTING WINDOWS ---------------- FBSS (DOS) ONLY RUNS UNDER MICROSOFT WINDOWS IF IT IS RUNNING IN THE 386 ENHANCED MODE. THIS MODE PROVIDES BOTH ACCESS TO THE VIRTUAL MEMORY CAPABILITIES OF THE INTEL 80386 PROCESSOR, ENABLING MICROSOFT WINDOWS APPLICATION PROGRAMS TO USE MORE PHYSICALLY AVAILABLE MEMORY, AND MULTITASKING OF NON-WINDOWS APPLICATION PROGRAMS. MICROSOFT WINDOWS INIT. PARAMETERS RELATED TO FBSS (DOS) -------------------------------------------------------- MICROSOFT WINDOWS PROVIDES AN INITIALIZATION FILE CALLED "SYSTEM.INI" TO DEFINE THE ENVIRONMENT. WITHIN THIS FILE THERE ARE SOME PARAMETERS THAT CAN AFFECT FBSS (DOS) BEHAVIOR UNDER MICROSOFT WINDOWS. PARAMETERS WHICH MUST BE SET TO A FIXED VALUE: - ALLVMSEXCLUSIVE=<FALSE> - WINEXCLUSIVE=<NO> - NETASYNCHFALLBACK=<TRUE> - UNIQUEDOSPSP=<TRUE> - INDOSPOLLING=<NO> - REFLECTDOSINT2A=<TRUE>. PARAMETERS WHICH MUST BE SET TO YOUR SPECIFIC ENVIRONMENT: - WINTIMESLICE=<100,50> - NETASYNCHTIMEOUT=<5.0> - NETHEAPSIZE=<8> - PERVMFILES=<50> - INT28CRITICAL=<FALSE> - COM1BASE=3FAH (FOR PR47X2## SERVER) (SEE DOCUMENTATION FILES IN THE PS/2 CONFIGURATION DISKETTE) - PSPINCREMENT=<2>. FOR A COMPLETE DESCRIPTION OF THE PARAMETERS SEE THE MICROSOFT WINDOWS DOCUMENTATION. FBSS (DOS) AND MICROSOFT WINDOWS SCENARIO ----------------------------------------- FBSS (DOS) KERNEL (SUPERVISOR AND SERVERS) RUNS ALONE UNDER MICROSOFT WINDOWS IN A DOS VIRTUAL MACHINE (VM), AND HAS ACCESS TO THE WHOLE VM MEMORY SPACE. THE FBSS APPLICATION PROGRAM RUNS IN ANOTHER VM, AND CAN THEREFORE USE MUCH MORE MEMORY THAN RUNNING IN A DOS ENVIRONMENT ALONE. WHEN WORKING WITH WINDOWS, YOU CAN HAVE FOR EXAMPLE FBSS (DOS) KERNEL RUNNING IN VM1, AN FBSS-NON-WINDOWS APPLICATION PROGRAM RUNNING IN VM2, NON-FBSS-NON-WINDOWS APPLICATION PROGRAMS RUNNING IN OTHER VMS, AND WINDOWS-NON-FBSS APPLICATION PROGRAMS RUNNING IN THE SYSTEM VIRTUAL MACHINE AT THE SAME TIME. IN ORDER TO COMMUNICATE THE FBSS APPLICATION PROGRAM TO THE FBSS (DOS) KERNEL, TWO SPECIAL INTERFACES ( EHC1WIND AND EHC2WIND ) ARE SUPPLIED WITH FBSS (DOS) IN THE FBSS SUBDIRECTORY OF THE PS/2 WHERE FBSS IS INSTALLED. EHC1WIND MUST BE LOADED BEFORE MICROSOFT WINDOWS AND EHC2WIND MUST BE LOADED BEFORE THE FBSS APPLICATION PROGRAM IN THE CORRESPONDING VM. STARTING FBSS (DOS) UNDER MICROSOFT WINDOWS ------------------------------------------- TO START MICROSOFT WINDOWS IN ENHANCED MODE, THE CONFIG.SYS FILE MUST BE CONFIGURED ACCORDING TO THE MICROSOFT WINDOWS USER'S GUIDE. THE GENERATED CONFIG.SYS SHOULD BE COMPLEMENTED WITH THE FBSS STATEMENTS REQUIRED FOR EACH ENVIRONMENT. AUTOFBSS.BAT MUST BE RUN INTO A VM AND MUST INCLUDE THE FOLLOWING STATEMENTS: - SHRDIRDD (ONLY FOR REMOTE LOG IF REQUIRED) - LOADER(E) SERVERNAME - LOADER(E) SERVERNAME - LOADER(E) SERVERNAME - ... - LOADER SPV.EXE/PARAMETERS - FBHLLAPI (IF REQUIRED) - FILESYS PARAMETERS (ONLY FOR REMOTE LOG IF REQUIRED) TO START THE WHOLE ENVIRONMENT AUTOMATICALLY, AUTOFBSS.PIF MUST BE CREATED ACCORDING TO THE MICROSOFT WINDOWS USER'S GUIDE. IT SHOULD RUN AUTOFBSS.BAT AND INCLUDE CORRECT VALUES TO RUN PROPERLY IN THE SPECIFIC WORKING ENVIRONMENT. IN ORDER NOT TO GET THE "MICROSOFT WINDOWS POP-UP PROGRAM SUPPORT" MESSAGE BOX, COMMAND.COM SHOULD BE ADDED IN THE AUTOFBSS.BAT FILE AFTER FBSS LOADING STATEMENTS. A SAMPLE OF AUTOFBSS.PIF FILE FOLLOWS: +-- 386 ENHANCED MODE OPTIONS -------------------------------+ ￝ ￝ ￝ PROGRAM FILENAME:...........C:\FBSS\AUTOFBSS.BAT ￝ ￝ WINDOW TITLE:...............FBSS KERNEL ￝ ￝ OPTIONAL PARAMETERS:........ ￝ ￝ START-UP DIRECTORY:.........C:\FBSS ￝ ￝ MEMORY REQUIREMENTS: KB REQUIRED...640 KB DESIRED...640 ￝ ￝ DISPLAY USAGE: FULL SCREEN......X EXECUTION: ￝ ￝ WINDOWED......... BACKGROUND....X￝ ￝ CLOSE WINDOW ON EXIT...X EXCLUSIVE.... ￝ ￝ ￝ ￝ MULTITASKING OPTIONS: ￝ ￝ BACKGROUND PRIORITY:...60 FOREGROUND PRIORITY:...100 ￝ ￝ DETECT IDLE TIME... ￝ ￝ ￝ ￝ MEMORY OPTIONS: ￝ ￝ EMS MEMORY: KB REQUIRED...0 KB LIMIT...0 LOCKED...￝ ￝ XMS MEMORY: KB REQUIRED...0 KB LIMIT...0 LOCKED...￝ ￝ USES HIGH MEMORY AREA... LOCK APPLICATION MEMORY...￝ ￝ ￝ ￝ DISPLAY OPTIONS: ￝ ￝ VIDEO MEMORY: TEXT..X LOW GRAPHICS.. HIGH GRAPHICS.. ￝ ￝ MONITOR PORTS: TEXT.. LOW GRAPHICS.. HIGH GRAPHICS.. ￝ ￝ EMULATE TEXT MODE... RETAIN VIDEO MEMORY... ￝ ￝ ￝ ￝ OTHER OPTIONS: ￝ ￝ ALLOW FAST PASTE... ALLOW CLOSE WHEN ACTIVE... ￝ ￝ RESERVE SHORTCUT KEYS: ALT+TAB... ALT+ESC...X CTRL+SPACE..￝ ￝ PRTSC..... ALT+PRTSC.. ALT+SPACE...￝ ￝ ALT+ENTER.. ￝ ￝ APPLICATION SHORTCUT KEY:....CTRL+F1 ￝ ￝ ￝ +------------------------------------------------------------+ YOU CAN CREATE A PIF FILE FOR THE FBSS APPLICATION PROGRAM. IT SHOULD BE A BAT FILE INCLUDING BOTH THE EHC2WIND INTERFACE AND THE APPLICATION PROGRAM. THE PIF SETTINGS ARE SIMILAR TO THOSE SHOWN ABOVE BUT SPECIFICALLY CUSTOMIZED FOR THE APPLICATION PROGRAM. LOADING RETURN CODES -------------------- IN ADDITION TO THE LOADING RETURN CODES DESCRIBED IN THE INSTALLATION AND CUSTOMIZATION MANUAL (SC19-5173), THE FOLLOWING RETURN CODES CAN APPEAR WHEN LOADING FBSS (DOS) IN A MICROSOFT WINDOWS ENVIRONMENT: +------------+------------+-----------------+------+----------+ ￝RETURN CODE ￝RETURN CODE ￝ EXPLANATION ￝ ACTION ￝ ￝ (HEX.) ￝ (DECIMAL) ￝ ￝ ￝ ------------+------------+-----------------+------+---------- ￝ ￝ ￝ YOU ARE TRYING ￝ LOAD EHC1WIND ￝ ￝ ￝ ￝ TO LOAD EHC1WIND￝ BEFORE FBSS AND ￝ ￝ ￝ ￝ WHEN WINDOWS OR ￝ WINDOWS. LOAD ￝ ￝ X '46' ￝ 70 ￝ PART OF FBSS￝ EHC2WIND IN THE ￝ ￝ ￝ ￝ (DOS) IS ALREADY￝ FBSS APPLICATION￝ ￝ ￝ ￝ LOADED OR EHC2￝ PROGRAM VIRTUAL ￝ ￝ ￝ ￝ WIND IN THE SAME￝ MACHINE. ￝ ￝ ￝ ￝ VM AS FBSS ￝ ￝ ￝ ￝ ￝ KERNEL. ￝ ￝ ------------+------------+-----------------+----------------- ￝ ￝ ￝ YOU ARE TRYING ￝ LOAD EHC1WIND AT￝ ￝ ￝ ￝ TO LOAD EHC2WIND￝ FIRST, THEN￝ ￝ ￝ ￝ AND EHC1WIND, OR￝ WINDOWS, AND￝ ￝ X '4E' ￝ 78 ￝ WINDOWS ARE NOT ￝ EHC2WIND AT LAST￝ ￝ ￝ ￝ LOADED. ￝ IN THE FBSS ￝ ￝ ￝ ￝ ￝ FBSS APPLICATION￝ ￝ ￝ ￝ ￝ PROGRAM VIRTUAL ￝ ￝ ￝ ￝ ￝ VIRTUAL MACHINE.￝ +------------+------------+-----------------+-----------------+ UNLOADING FBSS (DOS) -------------------- TO UNLOAD FBSS (DOS), THE FREE PROGRAM MUST BE RUN FROM THE APPLICATION PROGRAM VM AFTER EHC2WIND. SOME FBSS MODULES WILL BE REMOVED FROM MEMORY IF THE APPLICATION PROGRAM PERFORMS AN UNLOAD FBSS (DOS) (ES) SUPERVISOR FUNCTION. THE FREE PROGRAM REMOVES ONLY THE FBSS MODULES LOADED AFTER MICROSOFT WINDOWS. TO UNLOAD EHC1WIND, YOU MUST LEAVE MICROSOFT WINDOWS AND THEN ENTER FREE /W:1 . MIGRATION --------- CURRENT FBSS APPLICATION PROGRAMS AND USER-WRITTEN SERVERS MAY REQUIRE A FEW CHANGES TO RUN UNDER MICROSOFT WINDOWS. THOSE CHANGES ARE: - IF THE APPLICATION PROGRAM OR THE USER-WRITTEN SERVER USES THE CPRB/SEND_REQUEST OR THE COMAREA/DATAREA INTERFACE, IT MUST BE MIGRATED TO THE FBSS COMMON APPLICATION PROGRAMMING INTERFACE (API). THE COMMON API ALLOWS WRITING PROGRAMS PORTABLE AT THE SOURCE CODE LEVEL BETWEEN FBSS (DOS) AND FBSS/2. - WAIT FOR ASYNCHRONOUS EVENTS (WM) SUPERVISOR FUNCTION MUST BE USED INSTEAD OF THE EXIT TO IDLE STATUS (EX) SUPERVISOR FUNCTION. SINCE THE WM FUNCTION ALLOWS WAITING FOR A SPECIFIC EVENT, IT IS NO LONGER NECESSARY TO USE THE ACTIVATE DISPATCHER ENTRIES (SA) AND DEACTIVATE DISPATCHER ENTRY (RA) SUPERVISOR FUNCTIONS. - WHEN STARTING BOTH FBSS (DOS) AND THE APPLICATION PROGRAM AUTOMATICALLY THROUGH MICROSOFT WINDOWS RULES, THE APPLICATION PROGRAM CAN START BEFORE FBSS (DOS) HAS ENDED ITS LOADING PROCEDURE. IN THIS CASE THE APPLICATION PROGRAM SHOULD CHECK FOR FBSS AVAILABILITY. RESTRICTIONS ------------ CURRENT IMPLEMENTATION OF FBSS (DOS) WITH MICROSOFT WINDOWS INVOLVES SOME RESTRICTIONS. THESE RESTRICTIONS ARE: - FBSS-MICROSOFT WINDOWS APPLICATION PROGRAMS ARE NOT SUPPORTED. - ONLY ONE FBSS APPLICATION PROGRAM PER WORKSTATION IS ALLOWED. - THE IBM 3270 EMULATOR LAN MANAGEMENT PROGRAM IS NOT SUPPORTED. THIS MEANS THAT ALERTS GENERATED BY THE LAN ADAPTERS WILL NOT BE COLLECTED BY THE SYSTEM MANAGER SERVER. - ACCESS TO THE SHARED DOS DIRECTORY SERVER IS SUPPORTED ONLY IF IBM DOS VERSION 5.0, OR HIGHER, IS INSTALLED. THE SHRDIRDD AND FILESYS COMMANDS SHOULD BE LOADED, IF NEEDED, IN THE FBSS APPLICATION PROGRAM VM, JUST AFTER EHC2WIND AND BEFORE THE FBSS APPLICATION PROGRAM. WHEN USING REMOTE LOG FOR THE SHARED FILE, THEY SHOULD BE LOADED IN THE FBSS KERNEL VM AS WELL. - NO UTILITY PROGRAMS OR ADDITIONAL PROGRAMS SHOULD BE LOADED IN THE FBSS KERNEL VM. THEY SHOULD BE STARTED IN OTHER VMS. - TO MOVE FROM THE FBSS APPLICATION PROGRAM TO THE 3270 EMULATOR, TWO HOTKEYS ARE REQUIRED. THE FIRST ONE TO MOVE FROM THE FBSS APPLICATION PROGRAM VM TO THE FBSS KERNEL VM: THE SECOND ONE TO ACTIVATE THE 3270 EMULATOR. IF THE APPLICATION PROGRAM USES THE SIMULATE HOTKEY (EE) SUPERVISOR FUNCTION, ONLY THE FIRST HOTKEY IS NEEDED TO ACTIVATE THE 3270 EMULATOR. IN ANY CASE, TWO HOTKEYS ARE REQUIRED TO MOVE BACKWARDS. THE SAME EXPLANATION APPLIES TO THE FOLLOWING FBSS COMPONENTS: - OPERATOR INTERFACE - SYSTEM MANAGER OPERATOR - DIAGNOSTIC DEBUGGING TOOL (DDT). - ALL THE FBSS OPERATORS SHOULD BE IN THE BACKGROUND WHILE WORKING WITH THE FBSS APPLICATION PROGRAM AS USUAL. - TOKEN RING DATA LINK CONTROL (TRDLC), SYNCHRONOUS DATA LINK CONTROL (SDLC) AND 47X2 PRINTER SERVERS (PR47X2##) MUST BE LOADED BEFORE MICROSOFT WINDOWS, IF USED. - THE IBM X.25 INTERFACE CO-PROCESSOR/2 ADAPTER USED BY THE X.25 DATA LINK CONTROL (X25DLC) IS NOT COMPATIBLE WITH MICROSOFT WINDOWS. - FBSS T0 SUPERVISOR FUNCTION IS NOT SUPPORTED. - IBM 4717 MSR/E AND IBM 4718 PIN PAD ARE NOT SUPPORTED. - EHCR400 SERVER AND REMOTE CHANGE MANAGEMENT SERVICES SERVER ARE NOT SUPPORTED. THESE RESTRICTIONS APPLY ONLY IN THE WORKSTATIONS WHERE FBSS (DOS) AND MICROSOFT WINDOWS COEXIST. PERFORMANCE CONSIDERATIONS -------------------------- TO ACHIEVE MAXIMUM PERFORMANCE IN THE WHOLE ENVIRONMENT, YOU SHOULD ASSIGN THE MOST SUITABLE BACKGROUND/FOREGROUND PRIORITY VALUES TO FBSS KERNEL VM IN THE AUTOFBSS.PIF, DEPENDING ON THE SPECIFIC WORKING ENVIRONMENT. BESIDES, THE WINTIMESLICE SETTING IN SYSTEM.INI SHOULD BE THE MOST PROPER VALUE. ALTHOUGH 2MB OF MEMORY IS ENOUGH TO WORK IN 386 ENHANCED MODE, IT IS STRONGLY RECOMMENDED TO INSTALL 4MB AT LEAST. THE FBSS SUPERVISOR PARAMETER RELATED TO APPLICATION/SERVERS DISPATCHING DISTRIBUTION PERCENTAGE SHOULD BE SET TO THE DEFAULT VALUE. IBM FBSS (DOS) 3.1 AND IBM WINDOWS CONNECTION 2.03 FBSS HIGH LEVEL LANGUAGE API SUPPORT ALLOWS IBM WINDOWS CONNECTION TO RUN AS IF IT WAS RUNNING WITH OTHER SUPPORTED HLLAPI INCLUDED IN THE IBM WINDOWS CONNECTION DOCUMENTATION. IN ORDER TO WORK PROPERLY, FBSS KERNEL AND FBHLLAPI COULD BE INCLUDED INTO THE WINSTART.BAT FILE OR ELSE BE LOADED IN A DOS VIRTUAL MACHINE. IN THIS CASE INCLUDE EHC2WIND MODULE INTO THE WINSTART.BAT FILE AND LOAD EHC1WIND MODULE BEFORE MICROSOFT WINDOWS. ONLY ONE EMULATION SESSION IS SUPPORTED. REFER TO IBM WINDOWS CONNECTION AND MICROSOFT WINDOWS DOCUMENTATION FOR MORE DETAILS. THE RESTRICTIONS MENTIONED ABOVE ARE ALSO VALID IN THIS ENVIRONMENT.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II05190
Reported component name
PA LIB INFO ITE
Reported component ID
INFOPALIB
Reported release
001
Status
INTRAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
1991-07-24
Closed date
Last modified date
1991-10-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]
Document Information
Modified date:
13 December 2020