II02003: PMF COMMON PROBLEM INFO APAR

APAR status

• Closed as canceled.

Error description

• 566530701 HAU1102 R102 HAU1103 R103
  
  ********************  INDEX TO INFO APAR  ******************
  SECTION 1 - OLD PROBLEMS REAPPEAR AFTER INSTALLATION OF
              UY20749 PUT 8805 OY13764 PE'D UY90223
      ++HOLD FOR UY90223 AND UY20749 MAY HAVE BEEN IGNORED.
      TO ENSURE THAT THE INSTRUCTIONS IN THE COVER LETTER FOR
      OY13764 HAVE BEEN EXECUTED:
      1 - UPPER RIGHT HAND CORNER OF MAIN PMF PANEL SHOULD BE
          V1.132 OR HIGHER
      2 - CHOOSE OPTION 1 - FONT MANAGEMENT SERVICES
      3 - CHOOSE OPTION 2 - CHARACTER SET DEFINITION
      4 - PRINTER DEVICE TYPE ===> UNBOUNDED
      IF THE PRINTER DEVICE TYPE ===> 3800M3 OR 3820 THEN THE
      PTF HAS NOT BEEN INSTALLED CORRECTLY. REFERENCE BOTH
      APARS OY12274 AND OY13764 FOR MORE INFORMATION.
      *** IF THE PRINTER DEVICE TYPE ===> UNBOUNDED OR BOUNDED
          THEN PROCEED TO FOLLOWING DIAGNOSTIC TIPS
  SECTION 2: PMF INITIALIZATION PROBLEMS AND GENERAL INFORMATION
             ON HOW TO GATHER ERROR INFORMATION
  SECTION 3: DROPPING OUT OF PMF WHILE WORKING IN FONT MANAGEMENT
  SECTION 4: DROPPING OUT OF PMF WHILE WORKING IN OR TRYING TO
             ACCESS FORM MANAGEMENT
  SECTION 5: DROPPING OUT OF PMF WHILE BUILDING A PAGEDEF
  SECTION 6: PMF PERFORMANCE - CHARACTER GRAPHICS, INITIALIZATION,
                               OTHER AREAS
  SECTION 7: MISSING FIRST OR LAST LINE OF A PRINT DATA SET
  SECTION 8: WARNINGS
  SECTION 9: INCORROUT
  SECTION 10: PMF WITH ISPF
  ****************************************************************
  SECTION 1 - SEE ABOVE BEFORE PROCEEDING.......
  SECTION 2 - INITIALIZATION PROBLEMS AND ERROR INFORMATION
              GATHERING
  
      WHILE TRYING TO ACCESS PMF, YOU NEVER GET THE MAIN MENU BUT
  DROP BACK INTO TSO AND GET THE MESSAGE 'PRINT MANAGEMENT
  PROCESSING COMPLETE', THEN THE TSO READY MESSAGE IS DISPLAYED.
  
  TO REVEAL FURTHER INFORMATION ON THE PROBLEM YOU WILL NEED TO:
  
  LOCATE THE PMFD CLIST. DO NOT MAKE A COPY OF THE PMF CLIST.
  1. MODIFY THE 'PMFD' CLIST
  2. TURN MESSAGE TO ON  -  MSG(ON)
  3. CHANGE DEBUG TO 255  -  DE(255)
  4. CHANGE NOLIST, NOCONLIST, NOSYMLIST TO LIST, CONLIST,
     SYMLIST.
  5. TURN QUIET TO OFF  -  REMOVE THE STATEMENT IN THE APL
     INVOCATION SECTION THAT READS &Q, AND REMOVE THE CONTINUATION
     PLUS SIGN ON THE PREVIOUS LINE.   NOTE: THIS MAY CAUSE
     UNPREDICTABLE RESULTS AND EXTRA UNNECESSARY MESSAGES. IF
     YOU FEEL THAT BY REMOVING QUIET, MAJOR PROBLEMS ARE NOW
     OCCURING (ABENDS, OTHER INVOCATION PROBLEMS), TURN QUIET
     BACK ON.  WITH QUIET OFF, APL IS ABLE TO DISPLAY ALL THE
     MESSAGES IT WANTS TO, SO DON'T BE ALARMED IF YOU SEE A FEW
     INFORMATIONAL MESSAGES.
  
  IF YOU NOW SEE MESSAGES THAT WOULD INDICATE THE PROBLEM,
  PURSUE THE RESOLUTION OF THESE PROBLEMS.
  DON'T BE ALARMED, ESPECIALLY THE FIRST TIME YOU ARE TRYING
  TO BRING PMF UP, THAT YOU SEE TSO MESSAGES INDICATING THAT
  YOUR INTERNAL DATA SET (USERID.@D.DZJLIB) IS NOT CATALOGED
  OR CANNOT BE ACCESSED.  THIS IS NORMAL!!  IF THIS IS WHAT IS
  CAUSING YOU TO DROP INTO TSO OR APL, THEN YOU SHOULD PURSUE
  THIS PROBLEM.
  
  FINALLY, IF NO MESSAGES ARE REVEALED WHEN YOU ARE INITIALIZING,
  TYPE IN A ')MORE' WHEN IN APL (THE LETTERS MUST BE CAPITALIZED)
  TO SEE IF ANY MORE MESSAGE ARE REVEALED AND PURSUE IF NECESSARY.
  THEN TYPE IN ')SI' TO DISPLAY THE FUNCTION STACK.  RECORD THE
  STACK INFORMATION AND QUEUE TO LEVEL2 IF NECESSARY.
  
  ****************************************************************
  
  SECTION 3 - DROPPING INTO TSO OR APL WHEN IN FONT MANAGEMENT
              OR D/T3800 CONVERSION SERVICES.
  
  THIS IS USUALLY CAUSED BY YOUR REGION SIZE BEING TOO SMALL.
  PROCESSING RASTER PATTERNS AND DOING CHARACTER MANIPULATION
  REQUIRES A LOT OF STORAGE.  TRY TO INCREASE REGION SIZE
  (BE LIBERAL), OR DO THE SAME OPERATION ON A 'MUCH' SMALLER
  PATTERN OR CHARACTER TO SEE IF IT WORKS SUCCESSFULLY.  THIS
  WILL VERIFY THE STORAGE SIZE PROBLEM.
  
  ****************************************************************
  
  SECTION 4 - DROPPING INTO TSO OR APL WHEN TRYING TO ACCESS OR
              SAVE OUT OF THE COPY GROUP SCREEN IN FORM MANAGEMENT
  
  1. DROPPING OUT WHEN TRYING TO ACCESS THE SCREEN
     THIS HAPPENS WHEN YOU ARE USING A PMF 1.0 VERSION WORKSPACE
     WITH PMF 1.1 EXECLIBS.  THE COPY GROUP SCREENS AND FUNCTIONS
     WERE CHANGED FROM 1.0 TO 1.1, AND AN INCOMPATIBILITY WILL
     EXIST IF YOU MIX THE CODE.  CORRECT THE INSTALL PROBLEM.
  
  2. DROPPING OUT WHEN TRYING TO SAVE OUT OF THE SCREEN (PF3).
     THIS HAPPENS WHEN YOU ARE USING A PMF 1.1 VERSION WORKSPACE
     WITH 1.0 EXECLIBS.  THE SAME TYPE OF INCOMPATIBILITY EXISTS,
     BUT WITH DIFFERENT SYMPTOMS.  CORRECT THE INSTALL PROBLEM.
  
  ****************************************************************
  
  SECTION 5 - DROPPING INTO TSO OR APL WHEN BUILDING A PAGEDEF
  
  THIS IS CAUSED BY A MISSHAPED VARIABLE IN THE PAGE FORMAT
  DEFINITION, SUCH AS 'UNDERSCORED L'FPR.
  THE PROCEDURE YOU NEED TO CORRECT THIS SITUATION FOLLOWS:
  
  NOTE: THIS PROCEDURE IS IN REFERENCE TO PAGEDEFS SHIPPED WITH
        RELEASE 1.0 OF PSF, THE ONES SHIPPED IN SUBSEQUENT
        RELEASES SHOULD BE OK.
  
  14 OUT OF THE 27 IBM SUPPLIED PAGE FORMAT DEFINITIONS ARE IN
  ERROR.  THESE PAGE FORMAT DEFINITIONS CONTAIN A VARIABLE WHICH
  IS IMPROPERLY SHAPED.  ALSO, PAGEDEFS THAT ARE CREATED FROM
  A COPY OF THE IBM SUPPLIED PAGE FORMATS WILL BE IN ERROR.  THE
  ERROR WILL SURFACE WHEN A FONT NAME IS ADDED TO THE PAGE FORMAT
  DEFINITION, AND A PAGEDEF IS BUILT USING THE PAGE FORMAT.
  DURING THE BUILD PROCESS, THE USER WILL ABEND OUT OF PMF
  WITHOUT AN ERROR INDICATION AND DROP INTO TSO AS A RESULT OF
  THE BAD VARIABLE.
  
  THE IBM SUPPLIED PAGEDEFS RESIDE ON VSAPL.ADZJPLIB (IVP LIB
  NAME), AND ALSO ON VSAPL.DZJDMY1 IF THIS DATA SET WAS NOT
  DELETED AFTER PMF WAS INSTALLED.
  THE 14 MEMBERS ARE:  P2M16080  P2STD1  P2STD2  P2STD3
                       P204560  P205161  P206060  P206061
                       P206080  P206881  P208080  P208081
                       P26  P28
  
  THE PROCEDURE FOR CORRECTING THESE PAGE FORMAT DEFINITIONS IS
  AS FOLLOWS:
  
  1. ENTER PMF AND GO TO LIBRARY SERVICES (OPTION 6).  SELECT
     THE IMPORT OPTION (OPTION 1) AND IMPORT A COPY OF EACH OF
     THE PAGE FORMAT DEFINITIONS LISTED ABOVE FROM VSAPL.ADZJPLIB.
  
  NOTE: REFERENCE THE PMF USERS GUIDE OR PRESS PF1 FOR HELP
  
  2. AFTER YOU HAVE IMPORTED ALL OF THE BAD PAGE FORMATS INTO
     YOUR INTERNAL LIBRARY, GO BACK TO THE MAIN MENU AND ENTER
     ENTER PAGE MANAGEMENT SERVICES (OPTION 3). THEN ENTER THE
     PAGE FORMAT SECTION (OPTION 2).
  
  3. CHOOSE THE EDIT OPTION AND SELECT ONE OF THE BAD PAGE
     FORMATS THAT YOU IMPORTED.
  
  4. WHEN YOU HAVE THE PAGE FORMAT DISPLAYED, PRESS PF10 TO
     DISPLAY THE FONT LIST.
  
  5. WHEN THE FONT LIST IS DISPLAYED, PRESS PF3 TO SAVE IT.
     THIS WILL RESHAPE THE VARIABLE TO ITS CORRECT SHAPE.  PRESS
     PF3 AGAIN TO SAVE THE PAGE FORMAT.
  
  6. REPEAT STEPS 3 THRU 5 FOR EVERY PAGE FORMAT DEFINITION
     LISTED ABOVE.
  
  7. WHEN ALL OF THE PAGE FORMATS HAVE BEEN CORRECTED, GET OUT
     OF PAGE MANAGEMENT AND BACK INTO LIBRARY SERVICES WHERE YOU
     WILL EXPORT THESE MEMBERS BACK OUT TO VSAPL.ADZJPLIB, AND
     ALSO TO VSAPL.DZJDMY1 IF THIS DATA SET WAS NOT DELETED
     AFTER THE INSTALLATION OF PMF.  THE REPLACE OPTION MUST BE
     SPECIFIED SO THAT THE GOOD PAGE FORMATS REPLACE THE BAD ONES
     OUT ON THE DATA SET(S).
  
  NOTE: IF YOU HAVE ALREADY IMPORTED SOME OF THE BAD MEMBERS AND
    HAVE BUILT PAGEDEFS WITH THEM, THEN THESE NEW PAGEDEFS ALSO
    HAVE THE BAD VARIABLE. WHEN A FONT IS ADDED TO THESE
    PAGEDEFS AT A LATER DATE, THE PAGEDEF WILL NOT BUILD
    SUCCESSFULLY AND THE USER WILL ABEND OUT OF PMF AND INTO TSO.
       THE USER SHOULD DISPLAY THE FONT LIST FOR THE PAGE FORMAT
       DEFINITION WITHIN THAT PAGEDEF AND SAVE IT OFF TO RESHAPE
       THE VARIABLE.
  
  ****************************************************************
  
  SECTION 6 - PMF PERFORMANCE
  
  ***** REFERENCE APAR OY08481 WITH PTF UY12930 F708*****
  
  1. WHEN IN THE GRAPHIC CHARACTER EDITOR OF PMF, YOU HAVE THE
     OPTION OF VIEWING THE CHARACTERS AS SOLID OR OUTLINED
     IMAGES BY PRESSING PF5 OR 6(WHEN THE PROGRAMMED SYMBOLS
     FEATURE IS INSTALLED).
     WHEN THESE OPERATIONS ARE PERFORMED, THE FORCE COMMAND IS
     ISSUED TO GDDM FOR SECTIONS OF EVERY SCAN LINE.  THIS CAUSES
     THE IMAGE TO BE BUILT SCAN LINE BY SCAN LINE ON THE SCREEN
     SO THAT THE USER CAN SEE THE PROGRESS OF THE OPERATION.
     THIS OF COURSE CAUSES THE IMAGE TO BE BUILT SLOWER THAN IF
     IT WAS TOTALLY CONSTRUCTED, THEN DISPLAYED ON THE SCREEN.
     WITH CERTAIN TERMINALS, ESPECIALLY THE ONES WITH
     MICROPROCESSORS, THIS OPERATION IS EXTREMELY SLOW DUE TO THE
     AMOUNT OF TERMINAL PROCESSOR WORK THAT IS BEING DONE.
     THIS IS THE WAY PMF WAS INTENDED TO WORK.  THIS IS NOT A
     SERVICE CONSIDERATION, BUT A FUNCTION CONSIDERATION.  THE
     USER CAN SUBMIT A PASR(DESIGN CHANGE REQUEST) THROUGH
     MARKETING TO PURSUE A FUNCTION CHANGE.
  
  2. PMF INITIALIZATION TIME WILL BE INCREASED PROPORTIONALLY
     TO THE AMOUNT OF MAINTENANCE THAT HAS BEEN APPLIED.  THIS IS
     TRUE SINCE PMF DYNAMICALLY APPLIES MAINTENANCE TO THE BASE
     WORKSPACE EVERY TIME PMF IS BROUGHT UP.  YOU MAY SUBMIT A
     PASR(REQUEST FOR FUNCTION CHANGE) THROUGH MARKETING TO PURSUE
     A CHANGE IN THIS AREA.
  
  3. GENERAL RULE: ANY OPERATION HAVING TO DO WITH CHARACTER
     MANIPULATION OR GRAPHICS PROCESSING TAKES LONGER THAN OTHER
     OPERATIONS.
  
  4. PERFORMANCE DEGRADATION IS EXPERIENCED AFTER
     APPLYING PTF UY01002 PMF REL 1.1.  APAR
     OY12274 ADDRESSES THIS PROBLEM.
  
  ****************************************************************
  
  SECTION 7 - DROPPING FIRST OR LAST LINE OF A PRINT DATA SET
  
  THIS IS ACTUALLY NOT A PMF OR PSF PROBLEM, BUT A CONSIDERATION
  OF HOW THE PRINTER WORKS.
  CHARACTERS ARE ENCLOSED IN A CHARACTER BOX WHICH IS OF A UNIFORM
  SIZE THROUGHOUT THE FONT, AND ALL HAVE A BASELINE IN WHICH THE
  CHARACTERS REST ON, WHICH IS APPROXIMATELY LOCATED 2/3 DOWN FROM
  THE TOP OF THE BOX(CELL).  BOX HEIGHT ABOVE THE BASELINE IS
  CALLED THE ASCENDER, AND BELOW THE BASELINE IS CALLED THE
  DESCENDER AREA.  SINCE CHARACTERS ARE PLACED IN REFERENCE TO THE
  BASELINE, IT IS POSSIBLE TO PLACE A CHARACTER SO THAT EITHER
  THE TOP OR THE BOTTOM OF THE CHARACTER BOX EXTENDS OFF THE TOP
  OR BOTTOM OF THE PAGE INTO THE UNPRINTABLE AREA.
  WITH THE 3800 MODEL1 OR THE 3800 MODEL 3 IN COMPATABILITY MODE,
  THE PRINTER WOULD ONLY SHAVE OFF THAT PORTION OF THE BOX OR
  CHARACTER THAT EXTENDED INTO THE UNPRINTABLE AREA.  WITH THE
  MODEL3 IN PAGE MODE, IF ANY PART OF THE BOX EXTENDS INTO THE
  UNPRINTABLE AREA, THE WHOLE CHARACTER IS TRUNCATED.  THEREFORE,
  IF THE CHARACTERS IN YOUR FIRST OR LAST LINE EXTEND INTO THE
  UNPRINTABLE AREA, THE WHOLE LINE WILL BE LOST DUE TO TRUNCATION
  AT THE PRINTER.
  IF YOU TURN DATA CHECKS TO UNBLOCK IN THE PSF(566527501) WRITER
  PROC, YOU SHOULD SEE MESSAGES APPEAR THAT WILL TELL YOU THAT
  YOUR DATA HAS EXTENDED OFF THE PRINTABLE PAGE.  ALSO ENSURE
  THAT PIMSG=YES IN THE PROC ALSO.
  THIS SITUATION USUALLY OCCURS WHEN TOO LARGE OF A FONT IS USED
  FOR THE LINE SPACING SPECIFIED.  YOU SHOULD USE THESE FONTS FOR
  THESE LINE SPACING SPECIFICATIONS:
  6LPI = A FONT WITH A PITCH NO SMALLER THAN 10(ASCENDER OF 30 AND
         DESCENDER OF 10).
  8LPI = A FONT WITH A PITCH NO SMALLER THAN 12(12, 15, 20 ETC)
  10LPI = A FONT WITH A PITCH NO SMALLER THAN 15(15, 20 ETC)
  12LPI = A FONT WITH A PITCH NO SMALLER THAN 20(20, 24 ETC)
  NOTE: GT24 AND SOME 24 PITCH FONTS HAVE AN UNUSUALLY LARGE
        DESCENDER VALUE, AND SOMETIMES WILL CAUSE PRINT TO EXTEND
        OFF THE BOTTOM OF THE PAGE WHEN YOU WOULDN'T EXPECT IT TO.
  THIS IS A GENERAL GUIDE TO GO BY AND SHOULD NOT BE TAKEN AS A
  HARD AND FAST RULE IN CHOOSING A FONT.  THE BOTTOM LINE IS THAT
  YOU NEED TO SELECT A FONT THAT WILL WORK WITH YOUR PARTICULAR
  JOB.  YOU CAN LOOK AT THE FONT POSITION(FNP) STRUCTURED FIELD
  OF THE CHARACTER SET TO DETERMINE THE ASCENDER AND DESCENDER
  VALUES FOR THE FONT.  YOU CAN ALSO LOOK AT THE FIRST AND LAST
  LINE DESCRIPTOR(LND) STRUCTURED FIELDS IN YOUR PAGEDEF TO
  DETERMINE THE PLACEMENT POSITION WITHIN THE LOGICAL PAGE OF
  YOUR FIRST AND LAST LINES.  REMEMBER, THIS VALUE IS IN HEX AND
  THE PRINTER COUNTS FROM 0 WHEN PLACING LINES (A BASELINE
  POSITION VALUE OF X'1D'=29, BUT THE LINE WILL BE PLACED AT 30
  SINCE THE PRINTER COUNTS FROM 0 IN LINE PLACEMENT).
  REFERENCE THE PSF DATA STREAM REFERENCE MANUAL FOR MVS AND VSE
  TO FIND DESCRIPTIONS OF THE STRUCTURED FIELDS MENTIONED EARLIER.
  ***************************************************************.
  ***************************************************************
  SECTION 8 - WARNINGS
  1.  THE NOPROMT PARAMETER MUST BE SPECIFIED IN THE PMF CLIST
      AND PMFD CLIST.  RESPECIFING THIS PARAMETER TO PROMPT
      MAY RESULT IN SEVERE DATASET DAMAGE.REF APAR OZ96963.
  2. IF PSF FAILS AFTER INSTALLATION AND THE PROCEDURE INDICATED
     IN SECTION 1 REVEALS AN ABEND IN GDDM CHECK TO SEE IF
     PTF UP75898 (PE) IS INSTALLED ON THE SYSTEM. IT HAS BEEN
     REPORTED THAT IF THIS PARTICULAR PTF IS PRESENT PSF WILL
     FAIL TO INITIALIZE BECAUSE OUTPUT HAS BEEN ROUTED THROUGH
     GDDM USING A TOKEN NAME SPECIFIED IN A DEVICE CHARACTERISTIC
     TABLE.
  3. ABEND106 RC0C COULD RESULT IF 'FREESIZE' IS NOT LARGE
     ENOUGH.  DESCRIPTION OF THIS PARAMETER IS FOUND IN VS/APL
     FOR TSO: TERMINAL USER'S GUIDE, SH20-9180. THIS IS AN
     INSTALLATION CONCERN AND SHOULD BE PURSUED WITH SE.
  ***************************************************************.
  SECTION 9: INCORROUT
  INCORROUT TRYING TO EDIT A PAGE SEGMENT. PMF CAN ONLY EDIT
  SOURCE CODE, NOT OBJECT. OBJECT CODE IS A RESOURCE THAT IS
  ALREADY FORMATTED INTO AFPDS DATA. PMF CAN RELOAD THIS, BUT
  THE OUTPUT WILL BE INCORRECT. PLEASE REFER TO PAGES 3 THROUGH
  6 OF THE PMF USER'S GUIDE.
  SECTION 10: DUE TO ISPF STORAGE OVERHEAD, IT IS
  RECOMMENDED TO RUN PMF UNDER NATIVE TSO. IF YOU
  EXPERIENCE PROBLEMS WITH FALLING OUT OF PMF AND YOU
  ARE RUNNING UNDER ISPF, TRY REINVOKING PMF UNDER NATIVE
  TSO.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• THIS APAR WAS CREATED TO INCLUDE RESPONDER TEXT ON
  PROBLEMS WITH PMF AND MAY BE USED AS AN AID TO INSTALLING.
  ADDITIONAL SYMPTOMS: COPYGROUP
  

APAR Information

• 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