1 SYSTEM : UXP/V ********************************** PRODUCT-ID : ANALYZER * PTF DESCRIPTION * VERSION LEVEL: V12L10 ********************************** PTF LEVEL : L98031 PRODUCT CODE : B777LBC0-10-1 << SUMMARY >> 1. SOFTWARE PRODUCT: UXP/V ANALYZER V12L10 2. PTF NO. : L98031 3. ADDED FUNCTIONS NO FUNCTIONS ARE ADDED BY THIS PTF. 4. CANCELED RESTRICTIONS THE FOLLOWING RESTRICTION IS CANCELED BY THIS PTF: (1) USE OF THE FDB FUNCTION FOR AN EXECUTABLE FILE CREATED BY THE UXP/V C++ COMPILER 5. PTF APPLICATION TIME THE REQUIRED APPLICATION TIME IS 5 MINUTES. THE ABOVE TIME IS CALCULATED FROM THE NUMBER OF INPUT-OUTPUT OPERATIONS (* 30 MS) FOR APPLICATION OF THE PTF. 6. NUMBER OF FIXES : 3 FIXES 7. MANUAL UPDATES : N 8. MEMORY AND DASD SPACE REQUIREMENTS: CHANGED 9. CONDITIONS FOR APPLICATION : Y 10. INCOMPATIBILITIES : N 11. EFFECT ON PLF'S : N ----------------------------------------------------------------------- NOTES: Y: APPLICABLE N: NOT APPLICABLE (B777LBC0-10-1) 1 << PTF HISTORY >> --- --------- ------------------------------------------------------ NO. PTF LEVEL REMARKS --- --------- ------------------------------------------------------ 1 L97061 CANCELED RESTRICTION AND ERROR CORRECTION --- --------- ------------------------------------------------------ 2 L97121 ADDED FUNCTION, CANCELED RESTRICTION, AND ERROR CORRECTION --- --------- ------------------------------------------------------ 3 L98031 CANCELED RESTRICTION AND ERROR CORRECTION --- --------- ------------------------------------------------------ 1 <> NOTE: IN THE FOLLOWING DESCRIPTIONS, CHARACTERS BETWEEN @' AND ' ARE UPPER-CASE LETTERS. MESSAGES, COMMANDS, AND PATH NAMES ARE DISPLAYED ACTUALLY IN LOWER-CASE ON THE SCREEN IN SXO, UXP/M, AND UXP/V OPERATION. 1. PTF APPLICATION METHODS NOTE THE FOLLOWING WHEN APPLYING THIS PTF. THE FOLLOWING ARE EXECUTED AT RUN-LEVEL 1. 1.1 INSTALLATION OF SUPPLIED TAPE (1) INSTALL THE PRODUCT ON THE SUPPLIED TAPE IN THE SYSTEM. SPECIFY THE PATH NAME OF THE DAT UNIT AND UXP@'ANA', THE ABBREVIATED PRODUCT NAME. # PKGADD -D (*1) -A UXPPTF UXP@'ANA' ----------------------------------------- *1 SPECIFY THE PATH NAME OF A PATH NAME OF THE DAT UNIT. - FOR UXP/V BASIC PART V10L10 (1) X96011 OR EARLIER: /DEV/RST100 (2) OTHER THAN (1): /DEV/RST101 - FOR UXP/V BASIC PART V10L20 (1) WHEN CONVERTING FROM UXP/V V10L10 TO UXP/V V10L20 /DEV/RMT/0000-0C1010 (2) FOR UXP/V V10L20 (MULTIPLE IMPE SYSTEM) REFER TO THE SUPPLEMENTARY DOCUMENT FOR THE SOFTWARE RELEASE GUIDE FOR UXP/V BASIC PART V10L20 X96121. (2) TO BACK UP THE ANALYZER THAT IS INSTALLED IN THE SYSTEM, ENTER "Y" FOR THE FOLLOWING MESSAGE. _ _ WOULD YOU LIKE TO TAKE A BACKUP (DEFAULT: Y)!_Y,N,?,Q_!Y -- DO YOU USE DEFAULT DIRECTORY FOR BACKUP (DEFAULT: Y) _ _ !_Y,N,?,Q_!Y -- (3) THE FOLLOWING MESSAGE IS DISPLAYED TO ASK WHETHER THE JAPANESE MANUAL IS TO BE INSTALLED. TO INSTALL IT, ENTER "Y". - ONLINE MANUAL _ _ DO YOU WANT TO INSTALL JAPANESE ONLINE MANUAL!_Y/N?_!Y -- 1 (4) ENTER "Y" FOR THE FOLLOWING MESSAGE. DO YOU WANT TO CONTINUE WITH THE INSTALLATION OF THIS PACKAGE _ _ !_Y,N,?_!Y -- (5) WHEN THE FOLLOWING MESSAGE IS DISPLAYED, THE INSTALLATION IS COMPLETE. INSTALLATION OF WAS SUCCESSFUL. NOTE: THE LETTER N IN UXP@'ANA'.N IS A SEQUENTIAL NUMBER THAT IS INCREMENTED WITH EACH INSTALLATION. 11.3 CHECKING THE INSTALLATION THIS SECTION EXPLAINS THE PROCEDURE FOR VERIFYING THAT THE ANALYZER HAS BEEN INSTALLED CORRECTLY. AFTER THE OPERATION IN SECTION 1.1, DO NOT REBOOT THE SYSTEM. CONTINUE OPERATION AT RUN- LEVEL 1. USE THE PROCEDURES IN (1) FOR (2) TO CHECK THE INSTALLATION INFORMATION. (1) # PKGINFO -L UXP@'ANA'N --------------------- @'PKGINST': UXP@'ANA'.N @'NAME': @'ANALYZER' @'CATEGORY': APPLICATION @'ARCH': @'UXP/V' @'VERSION': @'V12L10 L98031' @'BASEDIR': / @'VENDOR': @'FUJITSU LIMITED' @'DESC': @'UXP/V ANALYZER' IS ANALYZER FOR @'UXP/V' @'F'ORTRAN90 /@'VP' @'UXP/V' @'F'ORTRAN90/@'VPP' @'UXP/V C' @'UXP/V C/VP' AND @'UXP/V C++' @'PSTAMP': @'FUJITSU PTF' @'M'ARCH 1998. @'INSTDATE': @'M'MM DD YYYY HH:MM @'VSTOCK': @'B777LBC0' @'STATUS': COMPLETELY INSTALLED @'FILES': 27 INSTALLED PATHNAMES 27 SHARED PATHNAMES 17 DIRECTORIES 4 EXECUTABLES 9599 BLOCKS USED (APPROX) MAKE SURE THAT THE @'NAME, VERSION, PSTAMP,' AND @'STATUS' COLUMNS ON THE DISPLAY ARE CORRECT. (2) # PKGCHK -N UXP@'ANA'.N ---------------------- NOTHING IS DISPLAYED IF THERE ARE NO INSTALLATION PROBLEMS. IF THERE IS AN INCONSISTENCY IN THE PKGINFO OUTPUT OR IF AN ERROR IS REPORTED BY PKGCHK, CONTACT A FUJITSU SERVICE ENGINEER. 11.4 CHECKING THE ONLINE MANUAL SOME CORRECTIONS ARE MADE TO THE ONLINE MANUAL BY THIS PTF. USE THE MAN COMMAND TO CHECK THAT THE ANALYZER ONLINE MANUAL HAS BEEN STORED CORRECTLY. USE THE PROCEDURE BELOW TO CHECK THE ANALYZER ONLINE MANUAL. (1) # MAN FDB ------- IF THE JAPANESE ONLINE MANUAL IS INSTALLED, SET THE LANG ENVIRONMENT VARIABLE TO JAPAN. OTHER PROCEDURES ARE THE SAME. (1) # @'LANG'=JAPAN ------------- (2) # EXPORT @'LANG' -------------- (3) # MAN FDB ------- 11.5 CHECKING WITH SAMPLE PROGRAM USE THE SAMPLE PROGRAM STORED IN /USR/LANG/SAMP/@'ANA' DURING INSTALLATION TO CHECK INSTALLATION OF THE ANALYZER. 1.5.1 CHECKING WITH THE SAMPLER 1.5.1.1 SAMPLER (SEQUENTIAL FORTRAN) (1) COMPILATION (1) # CD /USR/LANG/SAMP/@'ANA'/SAMPLER --------------------------------- (2) # ./FRTS.SH --------- (3) CHECK THAT TESTS.OUT WAS CREATED. (2) EXECUTION (1) THE FILE TESTS.SH IS A SH SCRIPT FOR CHECKING THE OPERATION OF TESTS.OUT AND FJSAMP. (2) PLACE THE SH SCRIPT IN (1) IN A PIPE QUEUE WHOSE AVAILABLE NUMBER OF PE IS ONE OR MORE. (3) AFTER EXECUTION, THE SAMPS.LIST ANALYSIS RESULT LIST IS DISPLAYED. CHECK THAT @'S'YNTHESIS @'I'NFORMATION IS OUTPUT. THE VALUES OF THE EXECUTION RESULT USUALLY DIFFER FROM THE VALUES IN SAMPS.LIST. REFER TO THE USER'S GUIDE FOR THIS SOFTWARE TO DETERMINE WHETHER THE EXECUTION RESULT IS VALID. 1.5.1.2 SAMPLER (PARALLEL FORTRAN) (1) COMPILATION (1) # CD /USR/LANG/SAMP/@'ANA'/SAMPLER --------------------------------- (2) # ./FRTP.SH --------- (3) CHECK THAT TESTP.OUT WAS CREATED. 1 (2) EXECUTION (1) THE FILE TESTP.SH IS AN SH SCRIPT FOR CHECKING THE OPERATIONS OF TESTP.OUT AND FJSAMP. (2) PLACE THE SH SCRIPT IN (1) IN A PIPE QUEUE WHOSE NUMBER OF AVAILABLE PES IS TWO OR MORE. (3) AFTER EXECUTION, THE SAMPP.LIST ANALYSIS RESULT LIST IS DISPLAYED. CHECK THAT @'P'ARALLEL @'I'NFORMATION IS OUTPUT. THE VALUES OF THE EXECUTION RESULT USUALLY DIFFER FROM THE VALUES OF THE SAMPP.LIST. REFER TO THE USER'S GUIDE FOR THIS SOFTWARE TO DETERMINE WHETHER THIS EXECUTION RESULT IS VALID. * IF THE EXECUTION RESULT COULD BE INCORRECT, CHECK THAT /USR/LANG/SAMP/@'ANA'/SAMPLER IS MOUNTED ON A NOAC MODE. IF IT IS MOUNTED ON AN AC MODE, CHANGE THE DIR THAT IS DEFINED BY SAMPP.SH TO THE DIRECTORY THAT IS MOUNTED ON THE NOAC MODE. 11.5.1.3 SAMPLER (C) (1) COMPILATION (1) # CD /USR/LANG/SAMP/@'ANA'/SAMPLER --------------------------------- (2) # ./VCC.SH -------- (3) CHECK THAT THE TESTC.OUT WAS CREATED. (2) EXECUTION (1) THE FILE TESTC.SH IS AN SH SCRIPT FOR CHECKING THE OPERATIONS OF TESTC.OUT AND FJSAMP. (2) PLACE THE SH SCRIPT OF (1) IN A PIPE QUEUE WHOSE AVAILABLE NUMBER OF PES IS ONE OR MORE. (3) AFTER EXECUTION, THE SAMPC.LIST ANALYSIS RESULT LIST IS DISPLAYED. CHECK THAT @'S'YNTHESIS @'I'NFORMATION IS OUTPUT. THE VALUES OF THE EXECUTION RESULT USUALLY DIFFER FROM THE VALUES IN THE SAMPC.LIST. REFER TO THE USER'S GUIDE FOR THIS SOFTWARE TO DETERMINE WHETHER THIS EXECUTION RESULT IS VALID. 1.5.1.4 SAMPLER (C++) (1) COMPILATION (1) # CD /USR/LANG/SAMP/@'ANA'/SAMPLER --------------------------------- (2) # ./@'CC'.SH ---------- (3) CHECK THAT TESTCPP.OUT WAS CREATED. (2) EXECUTION (1) THE FILE TESTCPP.SH IS AN SH SCRIPT FOR CHECKING THE OPERATIONS OF TESTCPP.OUT AND FJSAMP. (2) PLACE THE SH SCRIPT OF (1) IN A PIPE QUEUE WHOSE AVAILABLE NUMBER OF PES IS ONE OR MORE. (3) AFTER EXECUTION, THE SAMCPP.LIST ANALYSIS RESULT LIST IS DISPLAYED. CHECK THAT SYNTHESIS INFORMATION IS OUTPUT. THE VALUES OF THE EXECUTION RESULT USUALLY DIFFER FROM THE VALUES IN THE SAMCPP.LIST. REFER TO THE USER'S GUIDE FOR THIS SOFTWARE TO DETERMINE THIS EXECUTION RESULT IS VALID. 11.5.2 CHECKING FDB (1) COMPILATION (1) # CD /USR/LANG/SAMP/@'ANA'/FDB ----------------------------- (2) # ./CC.SH ------- (3) CHECK THAT TEST.OUT WAS CREATED. (2) EXECUTION (1) # /USR/LANG/BIN/FDB ./TEST.OUT ---------------------------- (2) CHECK THAT THE FOLLOWING MESSAGE IS DISPLAYED. _ @'FDB'!_@'F'UJITSU @'D'EBUGGER FOR @'C/C++' AND _ @'F'ORTRAN_! @'V'ERSION 12.10 PLEASE WAIT TO ANALYZE THE @'DEBUG' INFORMATION. . (3) ENTER "RUN" FOR THE FOLLOWING PROMPT: FDB* RUN --- (4) CHECK THAT THE FOLLOWING MESSAGES ARE OUTPUT: THE PROGRAM: ./TEST.OUT STARTING. HELLO WORLD]] THE PROGRAM: ./TEST.OUT TERMINATED. (5) ENTER "QUIT" FOR THE FOLLOWING PROMPT: FDB* QUIT ---- 11.5.3 CHECKING PFDB (1) COMPILATION (1) # CD /USR/LANG/SAMP/@'ANA'/PFDB > (4) ENTER "JOBEXEC -VP 2 -MEM 100" FOR THE FOLLOWING PROMPT: (0)FDB* JOBEXEC -VP 2 -MEM 100 LIST FUNCTION ! FUNC FILE: FUNCNAME 110.1.3 ENVIRONMENT VARIABLE (1) @'FDB_SRC_PATH' INDICATES A LIST OF DIRECTORY NAMES DELIMITED BY COLONS. WHEN THIS ENVIRONMENT VARIABLE IS SET, IT HAS THE PRECEDENCE OVER THE DIRECTORY USED AT COMPILATION THAT IS WRITTEN IN THE EXECUTABLE FILE OR THE CURRENT DIRECTORY DURING RETRIEVAL OF THE SOURCE FILES CONFIGURING THE SPECIFIED EXECUTABLE FILE. 10.1.4 EXPANSION OF CURRENT COMMAND (1) LIST FUNCTION ! FUNC FILE: FUNCNAME DISPLAYS TEN LINES SURROUNDING THE FUNCTION FUNCNAME. 110.1.5 COMMANDS SPECIFIC TO C++ (1) CATCHTYPE WHEN THE PRESENT POSITION IS IN THE TRY BLOCK AND AN EXCEPTION TRANSMISSION (THROW) IS PERFORMED AT THIS POSITION, THIS COMMAND DISPLAYS ALL THE TYPES AND LINES OF THE HANDLERS (CATCH) THAT CAN TRANSFER CONTROL AND RECEIVE THE EXCEPTION. (2) CATCH EXCEPTIONTYPE ! -A A BREAKPOINT IS SET IN THE TRANSMITTED (THROW) TYPE EXCEPTIONTYPE BEFORE THE STACK IS RELEASED WHEN CONTROL IS TRANSFERRED TO THE EXCEPTION HANDLER (CATCH). WHEN THE -A OPTION IS SPECIFIED, BREAKPOINTS ARE SET FOR ALL TRANSMISSION (THROW) TYPES. WHEN NO ARGUMENT IS SPECIFIED, THE TYPE SPECIFIED BY THE CATCH COMMAND IS DISPLAYED. (3) UNCATCH EXCEPTIONTYPE ! -A DELETES THE TYPE THAT IS SET BY THE CATCH COMMAND AT THE BREAKPOINT. WHEN THE TYPE EXCEPTIONTYPE THAT IS SET BY THE CATCH COMMAND IS SPECIFIED, ONLY THE SPECIFIED TYPE AT THE BREAKPOINT IS DELETED. WHEN THE -A OPTION IS SPECIFIED, ALL TYPES SET BY THE CATCH COMMAND FROM BREAKPOINTS ARE DELETED. WHEN NO ARGUMENT IS SPECIFIED, THE TYPE SET BY THE CATCH COMMAND IS DISPLAYED. (4) DEFTYPE CLASSNAME ! NAMESPACENAME ! TYPEDEFNAME DISPLAYS THE CLASS CLASSNAME, NAME SPACE NAMESPACENAME, AND TYPEDEF TYPEDEFNAME DEFINITIONS. (5) SHOW NAMESPACE DISPLAYS THE CURRENTLY VALID NAME SPACE NAME. (6) TYPEID VARIABLE ! *VARIABLE DISPLAYS THE TYPE NAME OF THE SPECIFIED VARIABLE. IF A VARIABLE SPECIFIED WITH AN ASTERISK INDICATES A MULTIPHASE CLASS, THE TYPE NAME OF THE OBJECT THAT IS INDICATED BY THE VARIABLE IS DISPLAYED. IN OTHER CASES, ALL TYPE NAMES EXCEPT THOSE WITH AN ASTERISK ARE DISPLAYED. 1 (7) BREAK -C CLASSNAME ! NAMESPACENAME SETS THE BREAKPOINT THAT IS SPECIFIED FOR THE FUNCTION DEFINED IN CLASS CLASSNAME OR IN NAME SPACE NAMESPACENAME. IF MORE THAN ONE FUNCTION FOR WHICH A BREAKPOINT IS SPECIFIED EXISTS IN THE CLASS OR NAME SPACE, A LIST OF FUNCTIONS IS DISPLAYED WITH SEQUENCE NUMBERS, SOURCE FILE NAME, CLASS NAME (MEMBER FUNCTION), AND ARGUMENTS. IF REENTRY IS REQUESTED, SPECIFY THE CORRESPONDING NUMBER FROM THE DISPLAYED LIST. (8) DELETE -C CLASSNAME ! NAMESPACENAME DELETES THE BREAKPOINT THAT IS SET FOR THE FUNCTION DEFINED IN CLASS CLASSNAME OR IN NAME SPACE NAMESPACENAME. IF TWO OR MORE FUNCTIONS FOR WHICH A BREAKPOINT IS SET EXIST IN THE CLASS OR IN THE NAME SPACE, A LIST OF FUNCTIONS IS DISPLAYED WITH SEQUENCE NUMBERS, SOURCE FILE NAME, CLASS NAME (MEMBER FUNCTION), AND ARGUMENTS. IF REENTRY IS REQUESTED, SPECIFY THE CORRESPONDING NUMBER FROM THE DISPLAYED LIST. 110.1.6 COMMANDS SPECIFIC TO C++ FOR THE CURRENT COMMAND (1) LIST FUNCTION ! FUNC FILE: FUNCNAME DISPLAYS TEN LINES SURROUNDING THE FUNCTION FUNCNAME. IF FUNCTION FUNCNAME CANNOT BE DEFINED UNIQUELY BECAUSE OF OVERLOAD, A LIST OF FUNCTIONS CORRESPONDING TO FUNCNAME IS DISPLAYED WITH SEQUENCE NUMBERS, SOURCE FILE NAME, CLASS NAME (WHEN IT IS MEMBER FUNCTION), AND ARGUMENTS. IF REENTRY IS REQUESTED, SPECIFY THE CORRESPONDING NUMBER FROM THE DISPLAYED LIST. IF A RETURN IS ENTERED, NO PROCESSING IS PERFORMED. (2) BREAK ! B FILE: LINE ALTHOUGH THE LINE NUMBER VALIDATES LINE NUMBER FOR THE MEMBER FUNCTION AND THE EXECUTION STATEMENT THAT ARE EXPANDED IN THE CLASS, THE CLASS IN THE INCLUDE FILE IGNORES THE LINE NUMBER. IN THIS CASE, IF A STATEMENT IS DESCRIBED OVER MULTIPLE LINES, THOSE LINES ARE MANIPULATED AS ONE LINE. (3) BREAK ! B FUNCNAME WHEN THE FUNCTION FUNCNAME CANNOT BE DEFINED UNIQUELY BECAUSE OF OVERLOAD, A LIST OF FUNCTIONS CORRESPONDING TO FUNCNAME IS DISPLAYED WITH SEQUENCE NUMBERS, SOURCE FILE NAME, AND ARGUMENTS. IF REENTRY IS REQUESTED, SPECIFY THE CORRESPONDING NUMBER FROM THE DISPLAYED LIST. IF A RETURN IS ENTERED, NO PROCESSING IS PERFORMED. (4) DELETE ! D FILE: FUNCNAME WHEN THE FUNCTION FUNCNAME CANNOT BE DEFINED UNIQUELY BECAUSE OF OVERLOAD, A LIST OF FUNCTIONS CORRESPONDING TO FUNCNAME IS DISPLAYED WITH SEQUENCE NUMBERS, SOURCE FILE NAME, AND ARGUMENTS. IF REENTRY IS REQUESTED, SPECIFY THE CORRESPONDING NUMBER FROM THE DISPLAYED LIST. IF A RETURN IS ENTERED, NO PROCESSING IS PERFORMED. 110.1.7 NOTES (1) REFERENCING THE FUNCTION NAME WHEN THE ARGUMENT EXCFILE IS AN EXECUTABLE FILE THAT IS LINKED DYNAMICALLY, THE FUNCTION NAME AND THE VARIABLES THAT ARE DEFINED IN THE SHARED LIBRARY CANNOT BE REFERENCED UNLESS THE SHARED LIBRARY IS LOADED TO THE PROCESS. THEREFORE, UNTIL THE MAIN FUNCTION IS CALLED, C/C++ LIBRARY FUNCTIONS CANNOT BE ACCESSED. (2) DISPLAYING VARIOUS INFORMATIONS THE FOLLOWING FUNCTIONS CANNOT BE USED BY PROGRAMS THAT ARE CREATED WITH THE UXP/V C LANGUAGE OR THE UXP/V C++ LANGUAGE: SHOW VL COMMAND AND SHOW OPT COMMAND (3) HANDLING OF FUNCTIONS IN THE INCLUDE FILE WHEN A FUNCTION IS DEFINED IN THE INCLUDE FILE IN THE C++ PROGRAM, AS, FOR EXAMPLE, THE SOURCE FILE AND THE INCLUDE FILE MUST BE IN THE SPECIFIED DIRECTORY. 1 PROGRAM TEMPORARY FIX REPORT PAGE 0001 *-----------------------------------------------------------------* ! SYSTEM NAME ! PRODUCT ID ! PRODUCT VL ! PTF NAME ! PAST PTFS ! *-----------------------------------------------------------------* ! UXP/V ! ANALYZER ! V12L10 ! L98031 ! NOT INCLUDE ! *-----------------------------------------------------------------* (A) 1.PROGRAM FIX 2.FEATURES ADDED 3.RESTRICTIONS CANCELED 4.CONFIGURATION CHANGED 5.OTHERS (B) 1.MODULE REPLACEMENT 2.OTHERS -NO.-PTF NO.--SDR NO.-COMPONENT----A-B-----------REMARKS------------- 0001 UL59884 P121700 SAMPLER 1 1 0002 UL60468 P121826 PFDB 1 1 0003 UL60469 P121869 FDB 3 1 0004 UL60469 P122724 FDB 4 1 ** END ** 1 PROGRAM TEMPORARY FIX LIST PAGE 0001 DESCRIPTION OF : 1.SYMPTOM 2.CAUSE 3.ACTION TAKEN 4.APPLICABLE CONDITIONS NO. PTF NO. SDR NO. COMPONENT FIX CLASSIFICATION SYMPTOM CODE -0001-UL59884 -P121700-SAMPLER --PROGRAM FIX-----------ABU - 1. A BUS ERROR OCCURS IN THE SAMPLER ANALYSIS PROCESSING UNDER THE FOLLOWING CONDITIONS: 1) A C-LANGUAGE PROGRAM IS ANALYZED, AND 2) THE PROGRAM CONTAINS A FUNCTION WITH A NAME OF 50 OR MORE CHARACTERS. 2. THE SAMPLER ANALYSIS PROCESSING CONTAINS AN ERROR. -0002-UL60468 -P121826-PFDB --PROGRAM FIX-----------IN - 1. UNUSUALLY, A JOB MAY FAILS UNDER THE FOLLOWING CONDITION: 1) THE EXECUTION OF JOBEXEC FAILS. 2. PFDB HANDLES A SIGNAL INCORRECTLY. 4. NONE -0003-UL60469 -P121869-FDB --RESTRICTIONS CANCELE--FX - 1. THE FDB FUNCTION WILL SUPPORT C++. 3. CANCEL OF RESTRICTION ** END **