UXP/V V10L20 X98061
1 SYSTEM : UXP/V
********************************** PRODUCT-ID : UXP/V
* PTF DESCRIPTION * VERSION LEVEL: V10L20
********************************** PTF LEVEL : X98061
PRODUCT CODE : B77710A0-20-1
<< SUMMARY >>
1. SOFTWARE PRODUCT: UXP/V V10L20
2. PTF NO. : X98061
3. ADDED FUNCTIONS
THERE ARE NO FUNCTIONS TO BE ADDED BY THIS PTF.
4. CANCELLED RESTRICTIONS
THERE ARE NO RESTRICTIONS TO BE CANCELLED BY THIS PTF.
5. PTF APPLICATION TIME
NOTE: IN THE FOLLOWING DESCRIPTIONS, CHARACTER BETWEEN @' AND '
ARE UPPER-CASE LETTERS. MESSAGES, COMMANDS, AND PATHNAMES
ARE DISPLAYED IN LOWER-CASE LETTERS ON THE SCREEN AT UXP/V
OPERATION.
THE FOLLOWING IS THE REQUIRED APPLICATION TIMES.
- A SINGLE @'IPL' GROUP SYSTEM : APPROX. 15 MINUTES
- TWO OR MORE @'IPL' GROUP SYSTEM :
APPROX. 15 MINUTES FOR X NUMBER OF @'IPL'GROUPS
THE ABOVE VALUE IS ESTIMATED ASSUMING VPP700, DAT DEVICE.
6. NUMBER OF FIXES : 58 FIXES
7. MANUAL UPDATES : N
8. MEMORY AND DASD SPACE REQUIREMENTS: CHANGED
9. CONDITIONS FOR APPLICATION : N
10. INCOMPATIBILITIES : Y
11. EFFECT ON PLF'S : Y
-----------------------------------------------------------------------
NOTES: Y: APPLICABLE N: NOT APPLICABLE
1
<< PTF HISTORY >>
NO. PTF LEVEL REMARKS
--- --------- ----------------------------------
1 X97031
2 X97061
3 X97091
4 X97121
5 X98031
6 X98061
--- --------- ----------------------------------
1
<< PTF DESCRIPTION >>
PREFACE
PLEASE ACQUIRE NECESSARY INFORMATION BEFORE THIS PTF IS APPLIED.
1. PTF APPLICATION INSTRUCTIONS
THE FOLLOWING ARE INSTRUCTIONS FOR APPLYING THIS PTF.
IT TAKES APPROX. 15 MINUTES TO APPLY THIS @'PTF' FOR A SINGLE @'IPL'
GROUP SYSTEM BY USING @'VPP700, DAT' UNIT AND APPROX. 15 MINUTES FOR
X NUMBER OF @'IPL' GROUPS FOR TWO OR MORE @'IPL' GROUP SYSTEM.
IN THE FOLLOWING DESCRIPTIONS, "<|" INDICATES CARRIAGE RETURN,
"/DEV/RMT/0000-0C1010" INDICATES THE ADDRESS OF THE TAPE DEVICE, AND
"/DEV/DSK/0000-0C4010" INDICATES THE ADDRESS OF THE SYSTEM DISK.
1) WHEN THIS PTF IS APPLIED FOR THE SINGLE @'IPL' GROUP SYSTEM,
FREE AREA IS REQUIRED IN /VAR/SADM AND /VAR/TMP.
THE REQUIRED FREE AREA IS DESCRIBED IN '5 DISK SPACE
REQUIREMENTS'.
WHEN THIS PTF IS APPLIED FOR TWO OR MORE @'IPL' GROUP SYSTEM,
FREE AREA IS REQUIRED IN /VAR/SADM, /VAR/TMP, AND /VAR/SPPL/PKG.
THE REQUIRED FREE AREA IS DESCRIBED IN '5 DISK SPACE
REQUIREMENTS'.
WHEN THE SINGLE @'IPL' GROUP SYSTEM CANNOT ALLOCATE THE REQUIRED
FREE AREA IN /VAR/SADM, PERFORM FROM 1-1) TO 1-5).
FOR TWO OR MORE @'IPL' GROUP SYSTEM, REFER TO SOFTWARE RELEASE
GUIDE.
REFER TO APPENDIX A A.3 'PROCEDURE FOR INSUFFICIENT SPOOL AREA'
IF IT IS IMPOSSIBLE TO ACQUIRE THE REQUIRED FREE AREA IN
/VAR/TMP, SPECIFY A DIRECTORY WITH FREE AREA IN AN ENVIRONMENTAL
VARIABLE @'TMPDIR'.
INSTANCE NAME: UXP@'V'
THE SYSGEN IS REQUIRED AFTER PACKAGE APPLICATION.
1-1) PREPARE THE DIRECTORY WITH AREA OF @'200M'BYTES OR MORE.
# MKFS -@'F' UFS /DEV/RDSK/0000-XXXXXXSX NNNNNN <|
------------------------------------------------
# MOUNT -@'F' UFS /DEV/DSK/0000-XXXXXXSX /MNT <|
----------------------------------------------
(*) /DEV/RDSK/0000-XXXXXXSX, /DEV/DSK/0000-XXXXXXSX INDICATES
THE DEVICE SPECIAL FILE THAT REFERS TO THE PARTITION ON
WHICH THE FILE SYSTEM IS TO BE CREATED.
(*) NNNNNN INDICATES THE SIZE OF REQUIRED FREE AREA.
IT IS SPECIFIED BY THE BLOCK SIZE.
1
1-2) COPY THE CONTENTS OF THE /VAR/SADM TO THE MINI DISK WHICH WAS
PREPARED ON 1-1.
# CD /VAR/SADM <|
---------------
# FIND . -DEPTH -PRINT ? CPIO -PDMU /MNT <| ?:PIPE
-----------------------------------------
1-3) UNMOUNT THE /VAR/SADM AND /MNT.
# CD / <|
-------
# UMOUNT /VAR/SADM <|
-------------------
# UMOUNT /MNT <|
--------------
1-4) EDIT THE /ETC/VFSTAB AND CHANGE THE DEVICE NAME OF /VAR/SADM
TO THE NAME WHICH WAS PREPARED ON 1-1.
# VI /ETC/VFSTAB <|
-----------------
1-5) MOUNT THE /VAR/SADM.
# MOUNT /VAR/SADM <|
------------------
* WHEN THE PROGRAM CORRECTION WILL BE APPLIED IN THE FUTURE,
USE THIS AREA. THEREFORE, FREE AREA IS REQUIRED. THE REQUIRED
FREE AREA IS USED THE PROGRAM CORRECTION WHICH WILL BE
APPLIED. IF IT IS IMPOSSIBLE TO ACQUIRE THE REQUIRED FREE
AREA, EXPAND REFFERING TO THE PROCEDURE SHOWN IN THIS
PARAGRAPH.
2) TO APPLY THE PACKAGE FOR THE SINGLE @'IPL' GROUP, PERFORM FROM
2-1) TO 2-6).
TO APPLY THE PACKAGE FOR TWO OR MORE @'IPL' GROUP, REFER TO
SOFTWARE RELEASE GUIDE AND COMPLETE THE INSTALLATION.
REFER TO APPENDIX A A.1 'PROCEDURE FOR INSTALLING A PACKAGE IN
TWO OR MORE @'IPL'GROOUP SYSTEMS'
* THERE IS NO PROBLEM THOUGH THE FOLLOWING MESSAGES MIGHT
BE OUTPUT WHILE INSTALLING THIS PACKAGE
@'WARNING': ALREADY BACKUP ...
@'WARNING': CAN NOT BACKUP. NOT FOUND ...
2-1) THE STATE SHOULD BE @'RUN LEVEL 1'.
2-2) MOUNT THE PTF TAPE TO THE MT UNIT, AND CONFIRM IF THE READY
LAMP IS ON.
1
2-3) APPLY THE PTF STORED IN THE MT TO THE SYSTEM.
# PKGADD -D /DEV/RMT/0000-0C1010 -A UXPPTF UXP@'V' <|
---------------------------------------------------
2-4) ENTER "Y" TO THE FOLLOWING MESSAGE.
DO YOU WANT TO CONTINUE WITH THE INSTALLATION OF THIS PACKAGE
Y <|
----
ALL RIGHTS RESERVED, @'COPYRIGHT (C) FUJITSU LIMITED' 1995-1998.
USING AS THE PACKAGE BASE DIRECTORY.
IF YOU WANT A BACKUP OF THE CURRENT SYSTEM,
IT WILL TAKE ABOUT 10 @'M' BYTES FREE DISK SPACES.
WHEN YOU WANT A BACKUP,
YOU CAN SPECIFY WHERE BACKUP FILES SHOULD BE PLACED.
WOULD YOU LIKE TO TAKE A BACKUP (DEFAULT: Y) Y <|
----
DO YOU USE DEFAULT DIRECTORY FOR BACKUP (DEFAULT: Y) Y <|
----
:
:
:
DO YOU WANT TO CONTINUE WITH THE INSTALLATION OF THIS PACKAGE
Y <|
----
* IN THE CHARACTERS OF THE ABOVE MESSAGE, < AND > MEANS A PAIR
OF SQUARE BRACKET.
2-5) IF THE FOLLOWING MESSAGE ARE OUTPUT, INSTALLATION IS COMPLETED
INSTALLATION OF WAS SUCCESSFUL.
2-6) MOREOVER, CONFIRM THE VALIDITY OF THE FILE TO WHICH THE PTF
HAS BEEN APPLIED.
# PKGCHK -N UXP@'V'.N <|
----------------------
* IF THERE IS NO PROBLEM WITH THE APPLICATION OF THIS PTF,
NOTHING WILL BE DISPLAYED.
1
3) CONFIRM THE INSTALLATION INFORMATION.
# PKGINFO -L UXP@'V'.N <|
-----------------------
@'PKGINST': UXP@'V'.N
@'NAME': @'UXP/V BASE PACKAGE'
@'CATEGORY': SYSTEM,UTILITY
@'ARCH': @'UXP/V'
@'VERSION': @'V10L20 X98061'
@'BASEDIR': /
@'VENDER': @'FUJITSU LIMITED'
@'DESC': @'UXP/V BASE PACKAGE V10L20 X98061 PTF'.
@'PSTAMP': @'FUJITSU PTF JUNE 1998'.
@'INSTDATE': (THE INSTALLATION DATE AND TIME)
@'VSTOCK': @'B77710A0'
@'STATUS': COMPLETELY INSTALLED
@'FILES': (OMITTED)
* THE NUMERIC CHARACTERS IN PACKAGE NAME DIFFER BY
WHICH PUF OR PEF HAS BEEN APPLIED TO THE BASIC PART OF THE
SYSTEM.
4) SDUMP(8) MUST BE REWRITTEN TO THE DISK OR TAPE BECAUSE SDUMP(8)
IS MODIFIED IN THIS PTF.
SO, PLEASE EXECUTE THE FOLLOWING:
REFER TO SETBOOT(1@'M') AND MKSTAND(1@'M') IN THE REFERENCE
MANUAL.
4-1) SET THE STANDALONE DUMP, EXECUTING SETBOOT(1@'M') COMMAND.
# /USR/UXP/SETBOOT -D /USR/UXPLIB/STANDALONE/SDUMP
--------------------------------------------------
/DEV/DSK/0000-0C4010S1 <|
-------------------------
4-2) GENERATE THE MAGNETIC TAPE PROGRAM FOR SDUMP, EXECUTING
MKSTAND(1@'M')
# /USR/UXP/MKSTAND /DEV/RMT/0000-0C1010 SDUMP <|
----------------------------------------------
5) RE-GENERATE THE KERNEL, EXECUTING SYSGEN(1@'M') COMMAND.
# SYSGEN <|
---------
6) SPECIFY SINGLE USER MODE, EXECUTING SHUTDOWN(1@'M') COMMAND.
# SHUTDUWN -G0 -Y <|
------------------
7) REPLACE THE KERNEL, EXECUTING NEWSYS(1@'M') COMMAND.
# NEWSYS <|
---------
NOW THE PTF APPLICATION IS COMPLETED.
1
2. MANUAL UPDATES
NONE.
3. INCOMPATIBILITIES
THE FOLLOWING ARE INCOMPATIBILITIES RESULTING FROM THIS PTF.
SEE THE ATTACHED 'INCOMPATIBILE ITEM SHEET'.
NO. INCOMPATIBILITY ID NUMBER REMARKS
--- ----------------------------------- ------------- ------------
1 MODIFICATION OF THE @'PE' NUMBER @'HUXV-00073'
AS SPECIFIED BY @'BKRS'
--- ----------------------------------- ------------- ------------
2 MODIFICATION OF MAIL SENDING AND @'HUXV-00074'
RECEIVING PROCESSING
--- ----------------------------------- ------------- ------------
3 ENHANCEMENT OF CHECKING THE HARD @'HUXV-00075'
LINK FILE OF MAILS
--- ----------------------------------- ------------- ------------
4. CONDITIONS FOR APPLICATION
NONE.
5. DISK SPACE REQUIREMENTS
THE TABLE BELOW SHOWS THE CHANGE IN THE SIZE OF USED AREA IN THE
SYSTEM FILE AFTER THIS PTF HAS BEEN APPLIED: *1
NO. STANDARD DIRECTORY INCREMENT (BLOCKS) *2
--- ---------------------------------------- ---------------------
1 /VAR/SADM/PKG/UXP@'V.'N 136
--- ---------------------------------------- ---------------------
2 SAVED DIRECTORY 8800
(DEFAULT: /VAR/SADM/PKG/UXP@'V.'N/SAVE)
--- ---------------------------------------- ---------------------
*1 ANOTHER 45000-BLOCK AREA UNDER /VAR/TMP AND /VAR/SPOOL/PKG
RESPECTIVELY IS TEMPORARILY USED.
*2 BLOCK SIZE IS 512 BYTES.
6. ADDED FUNCTIONS
NONE.
7. CANCELLED RESTRICTIONS
NONE.
1
8. SUPERSEDED PUF'S
THE FOLLOWING PUF'S HAVE BEEN SUPERSEDED BY THIS PTF OR WILL BE
SUPERSEDED BY FUTURE PTF'S.
NO. PUF *1 COMPONENT PTF LEVEL REMARKS *2
--- ---------- ----------------- --------- --------
1 @'UX14301' @'FS,NFS,VFL-FS' X98061 Y
2 @'UX14332' @'NET' X98061 Y
3 @'UX14377' @'IOS' X98061 Y
--- ---------- ----------------- --------- --------
*1 THE PUF NUMBER FOR THE LATEST PTF LEVEL WHEN MORE
THAN ONE PUF HAS BEEN ISSUED FOR THE ERROR
*2 Y: SUPERSEDED BY THIS PTF
N: SUPERSEDED BY FUTURE PTF'S
9. EFFECT ON PLF'S
1) THIS PTF AFFECTS THE FOLLOWING PLF'S.
NO. PLF EFFECT RE-ISSUED PLF
-- ----------- ------------------------- ---------------
1 @'L055717' INVALIDATED BY THIS PTF. L355717
-- ----------- ------------------------- ---------------
10. OTHERS
10.1 NOTES ON SOFTWARE RELEASE GUIDE
10.1.1 PRECAUTIONS
THE FOLLOWING PRECAUTIONS ARE ADDED.
:--+------------------+----------------------------------------------+
:NO:COMMAND NAME, ETC.: :
: +------------------+ PRECAUTIONS :
+--+----------------+------------------------------------------------+
: 1: ATM.CONF(4) : :
: +----------------+ :
: : ERROR EXIST IN ATM.CONF(4) REFERENCE MANUAL. :
: : ATM.CONF(4) IS @'ATM' ADAPTER CONFIGURATION INFORMATION FILE :
: : :
: : -------+--------------------------------------------------------+
: : WRONG :@'EXAMPLES' :
: : : .....OMISSION..... :
: : : UNIT:0, PHYMODE:@'SDH', BANDWIDTH:VCI=100/RATE=20 :
: : : VCI=101/RATE=80 :
: : -------+--------------------------------------------------------+
: : CORRECT:@'EXAMPLES' :
: : : .....OMISSION..... :
: : : UNIT:0, PHYMODE:@'SDH', BANDWIDTH:VCI=100/RATE=20/ :
: : : VCI=101/RATE=80/ :
+--+-----------------------------------------------------------------+
1
10.1.2 NOTES ON USING THE JOB SWAP FUNCTION
1. ABOUT THE CASE WHERE @'PE' WHERE A JOB SWAP AREA EXISTS DOWNED
IF @'IOPE' CONTAINING A JOB SWAP AREA FAILS, THE FOLLOWING
SYMPTOM MAY OCCUR:
- HIGH PRIORITY JOBS CANNOT BE @'RUN'.
IN THIS EVENT, THE FOLLOWING MESSAGE IS OUTPUT TO THE CONSOLE:
@'JOBSWAP:0408': JOB SWAPOUT: VNODE CREATE FAILED (ERROR #),
AREA = #, BLKNUM = #
THE NAME OF THE JOB SWAP AREA IN THE FAILING @'PE' IS INDICATED AT
"AREA".
THIS PHENOMENON OCCURS UNDER THE FOLLOWING CONDITIONS:
1) THE JOB SWAPPED OUT TO THE JOB SWAP AREA EXISTS ON A FAILED
@'IOPE'.
2) THE VECTOR MEMORY OF THE ABOVE JOB IS NOT SWAPPED OUT.
3) THE VECTOR MEMORY OF THE ABOVE JOB MUST BE SWAPPED OUT TO RUN
HIGH PRIORITY JOBS.
IF THE VECTOR MEMORY OF THE JOB IS NOT SWAPPED OUT AFTER THE FIRST
SWAP-OUT, THE VECTOR MEMORY IS LATER SWAPPED OUT.
THE VECTOR MEMORY IS SWAPPED OUT TO THE JOB SWAP AREA USED FOR THE
FIRST SWAP-OUT. CONSEQUENTLY, WHEN THE @'IOPE' CONTAINING THE JOB
SWAP AREA USED FOR THE FIRST SWAP-OUT FAILS, THE VECTOR MEMORY
CANNOT BE SWAPPED OUT.
IN THE ABOVE CASE, THE VECTOR MEMORY CANNOT BE SWAPPED OUT, AND
HIGH PRIORITY JOBS CANNOT BE @'RUN'.
WHEN THE ABOVE-MENTIONED PHENOMENON IS GENERATED, IT IS CANCELED
BY DOING THE FOLLOWING ACTIONS.
- RAISE THE MEMORY PRIORITY OF THE JOB WHICH IS SWAPPED-OUT TO
THE JOB-SWAP AREA ON DOWNED @'PE'. THE MEMORY PRIORITY OF
THE JOB SHOULD BE HIGHEST.
IN THE ABOVE, THE JOB WHICH IS SWAPPED OUT TO THE JOB SWAP AREA
ON A DOWNED @'PE' IS FORCIBLY TERMINATED AND RESOLVED.
WHEN THERE ARE TWO OR MORE JOB ARE SWAPPED-OUT TO THE JOB-SWAP
AREA ON DOWNED @'PE', REPEAT THE OPERATION OF THE ABOVE-MENTIONED
FOR EACH JOB.
2. ABOUT THE CASE TO USE @'VFL-FS' AS A JOB SWAP AREA
WHEN @'VFL-FS' IS USED AS A JOB SWAP AREA, A SWAP FILE IS
ALLOCATED TO THE CONTINUOUS AREA. THEREFORE, WHEN FRAGMENTATION
ADVANCES BY REPEATING JOB SWAP-OUT AND SWAP-IN, THE SWAP FILE MAY
NOT BE ALLOCATED AND SWAP-OUT BECOMES UNABLE EVEN WHEN THERE IS
CAPACITY LEFT IN THE JOB SWAP AREA.
1
2.1 METHOD OF JUDGING THE OCCURRENCE OF FRAGMENTATION IN A JOB SWAP
AREA
WHEN A JOB CANNOT BE SWAPPED OUT TO A PARTICULAR AREA BECAUSE OF
FRAGMENTATION, THE FOLLOWING MESSAGE IS DISPLAYED ON THE CONSOLE.
@'JOBSWAP:0408': JOB SWAPOUT: VNODE CREATE FAILED (ERROR 28)
AREA = #1, BLKNUM = #2
#1 A JOB SWAP AREA NAME / A FILE NAME
#2 THE NUMBER OF BLOCKS WHICH TRIED TO BE ALLOCATED AS A JOB
SWAP FILE
AT THIS TIME, EACH VALUE OF FOLLOWING A AND B IS CONFIRMED, AND
IF THE VALUE OF A IS A VALUE OF B OR MORE, THIS PHENOMENON IS
GENERATED.
A) CONFIRM THE VALUE OF "REMAINING SIZE" OF THE JOB SWAP AREA
WHICH OUTPUT IN THE MESSAGE BY -L OPTION OF JOBSWAP(1@'M').
B) CALCULATE THE SIZE OF THE AREA WHICH TRIED TO BE ALLOCATED
AS A JOB SWAP FILE FROM THE NUMBER OF BLOCKS WHICH OUTPUT
IN THE MESSAGE.
THIS VALUE CAN BE CALCULATED BY THE FOLLOWING METHOD.
(BLOCK NUMBER) *
(BLOCK SIZE OF @'VFL-FS' USING AS A JOB SWAP AREA)
2.2 RESPONSE TO JOB SWAP FAILURE DUE TO FRAGMENTATION
WHEN A SWAP-OUT TO A PARTICULAR JOB SWAP AREA FAILS DUE TO
FRAGMENTATION, AND IF ANOTHER JOB SWAP AREA IS REGISTERED, THE
JOB IS AUTOMATICALLY SWAPPED OUT TO THE REGISTERED AREA.
THEREFORE, BY REGISTERING ANOTHER JOB SWAP AREA, A JOB SWAP
FAILURE DUE TO FRAGMENTATION CAN BE PREVENTED.
A JOB SWAP AREA IN WHICH FRAGMENTATION OCCURS IS ALSO USED FOR
THE SWAP-OUT OF A JOB WHICH CAN BE SWAPPED OUT TO A CONTINUOUS
AREA.
WHEN JOBS WHICH ARE SWAPPED OUT TO THE JOB SWAP AREA IN WHICH
FRAGMENTATION OCCURS ARE SWAPPED IN, THE FRAGMENTATION IS
CANCELED AND THE JOB SWAP AREA COMES TO BE USED AS WELL AS BEFORE
THE FRAGMENTATION OCCURS.
1
APPENDIX A PACKAGE INSTALLATION/DELETION PROCEDURE FOR TWO OR MORE
@'IPL' GROUP SYSTEMS
A.1 PROCEDURE FOR INSTALLING A PACKAGE IN TWO OR MORE @'IPL' GROUP
SYSTEM
A.1.1 PREFACE
THIS SECTION DESCRIBES THE PROCEDURE FOR INSTALLING A PACKAGE IN
TWO OR MORE @'IPL' GROUP SYSTEM.
USE THE /SBIN/@'P'PKGADD COMMAND TO INSTALL TWO OR MORE PACKAGES
IN TWO OR MORE @'IPL' GROUP SYSTEMS.
ALSO, CHECK THE FOLLOWING INFORMATION AT INSTALLING THE PACKAGE.
- INSTANCE NAME OF THE PACKAGE TO BE INSTALLED
- CAPACITY OF THE PACKAGE TO BE INSTALLED
- NECESSITY OF SYSGEN AND NEWSYS AFTER INSTALLING THE PACKAGE
A.1.2 PREREQUISITES
1) OPERATION FLOW
THE OPERATION FLOW IS AS FOLLOWS:
(1) DEVELOP THE PACKAGE WITH THE SPOOL DIRECTORY (PKGTRANS).(*1)
(2) INSTALL THE PACKAGE IN PRIMARY @'PE' (@'P'PKGADD).
(3) CHANGE THE SYSTEM TO THE MAINTENANCE @'IPL' GROUP(*2)
(MAINTMODE).
(4) INSTALL THE PACKAGE IN THE SYSTEM DISK OF EACH @'IMPE'
(@'I'PKGADD).
(5) CANCEL THE MAINTENANCE @'IPL' GROUP (MAINTMODE -R).
*1 READ THE @'PTF' AND @'PUF' MANUALS OF THE PACKAGE TO BE
INSTALLED TO CHECK THE DEPENDENCE RELATION OF THE PACKAGE AND
DETERMINE THE INSTALLATION ORDER.
ALSO CONSIDER THE FOLLOWING *6 AND *7.
*2 THE MAINTENANCE @'IPL' GROUP IS THE ENTIRE SYSTEM STARTED UP
AS ONE @'IPL' GROUP. ALL @'IMPE' SYSTEMS SHARE THE SYSTEM
DISK OF THE PRIMARY @'PE'.
2) SPECIFYING A DEVICE
WHEN EXECUTING THE @'P'PKGADD COMMAND, THE DEVICE QUERIES AS
FOLLOWS:
IN THE FOLLOWING CODING, THE LINES ENDING WITH 'RET' REQUIRE
SOME OPERATION.
+------------------------------------------------------------------+
: # @'P'PKGADD 'RET' :
: PLEASE ENTER @'DEVICE (DEFAULT /VAR/SPOOL/PKG): :
+------------------------------------------------------------------+
<>:SQUARE BRACKET
1
TWO OR MORE PACKAGES CAN BE INSTALLED IN TWO OR MORE @'IPL' GROUP
SYSTEMS IF THE FOLLOWING OPERATIONS ARE EXECUTED. A DIRECTORY
FORMAT DEVELOPS TWO OR MORE PACKAGES TO BE INSTALLED IN THE SPOOL
DIRECTORY. ONCE THE @'P'PKGADD COMMAND IS EXECUTED,THIS SPOOL
DIRECTORY IS SPECIFIED FOR A DEVICE.
THE SPECIFIED SPOOL DIRECTORY MUST SATISFY THE FOLLOWING
CONDITIONS:
1. THE SPOOL DIRECTORY HAS A SUFFICIENT AMOUNT OF SPACE TO DEVELOP
THE PACKAGE TO BE INSTALLED.
2. THE SAME DIRECTORY WITH SUFFICIENT CAPACITY MUST BE IN THE
SYSTEM DISK OF EACH @'IMPE'.
THE SPACE DESCRIBED HERE IS A TOTAL VALUE OF THE SPACES DESCRIBED
IN THE @'PTF' AND @'PUF' MANUALS OF THE PACKAGE TO BE INSTALLED.
IF THE INSTANCE NAME OF THE PACKAGE TO BE INSTALLED IS THE SAME,
NOTE THE DEPENDENCE RELATION WHEN INSTALLING THE PACKAGE.
*3 THE @'OS' CONSOLE IS REQUIRED TO INSTALL OR DELETE THE PACKAGE
*4 THE @'P'PKGADD COMMAND IS USED IN THE SINGLE USER MODE.
THE @'P'PKGADD COMMAND EXECUTES THE MOUNTALL COMMAND
INTERNALLY. WHEN A PARTITION OTHER THAN THE SYSTEM DISK IS
SPECIFIED FOR THE SPOOL DIRECTORY, NOTE THE FOLLOWING POINTS.
WHEN "NO" IS SPECIFIED IN THE AUTOMNT FIELD OF THE
/ETC/VFSTAB FILE, THE MOUNTALL COMMAND DOSE NOT MOUNT
AUTOMATICALLY. IN THIS CASE, THE USER MUST MOUNT USING THE
MOUNT COMMAND. OTHERWISE, SPECIFY "YES" IN THE AUTOMNT FIELD
OF THE PARTITION WHICH CORRESPONDS TO THE /ETC/VFSTAB FILE
USING THE EDITOR. NEXT,EXECUTE THE @'P'PKGADD COMMAND.
*5 WHEN USING THE PS COMMAND WHILE THE MAINTENANCE @'IPL' GROUP
IS OPERATING, EXECUTE PS -@'X' ON THE PRIMARY @'PE' FIRST.
IF NOT, THE PROCESS EXECUTED ON THE CONSOLE IS NOT DISPLAYED.
3) WHEN THE SYSTEM CONFIGURATION CHANGES
REFLECT THE SYSTEM CONFIGURATION CHANGE ON THE /ETC/IPLTBL.MAINT
FILE WHEN THE CONFIGURATION AFFECTING @'IMPE'S OF THE SYSTEM IS
CHANGED AND THE /ETC/IPLTBL FILE IS EDITED.
SECTION A.5 DETAILS HOW TO CREATE THE /ETC/IPLTBL.MAINT FILE.
REFER TO SECTION A.5.
1
A.1.3 PREPARING THE INSTALLATION
1) DEVELOPING THE PACKAGE
DEVELOP THE PACKAGE TO BE INSTALLED WITH THE SPOOL DIRECTORY ON
THE PRIMARY @'PE'. READ THE @'PTF' AND @'PUF' MANUALS OF THE
PACKAGE TO BE INSTALLED TO CHECK THE DEPENDENCE RELATION OF THE
PACKAGE AND DETERMINE THE INSTALLATION ORDER.
SPECIFY /VAR/SPOOL/PKG FOR THE SPOOL DIRECTORY AND EXPAND
UXP@'SAMPLE DLIB'.
THE FOLLOWING EXAMPLE SHOWS THAT THE PACKAGE TO BE INSTALLED IS
UXP@'SAMPLE DLIB' OR UXP@'SAMPLE PUF'(THE PACKAGE HAS THE SAME
INSTANCE NAME AND DEPENDENCE RELATION AS THE UXP@'SAMPLE DLIB').
THE EXAMPLE ALSO SHOWS THAT THE MEDIUM IS A @'DAT' TAPE AND THE
TAPE DEVICE IS /DEV/RMT/0000-0C1010.
TO DEVELOP A PACKAGE WITH A DIRECTORY FORMAT, USE THE PKGTRANS
COMMAND.
+------------------------------------------------------------------+
: # PKGTRANS -N /DEV/RMT/0000-0C1010 /VAR/SPOOL/PKG 'RET' :
+------------------------------------------------------------------+
THE FOLLOWING MESSAGES ARE DISPLAYED. PRESS THE ENTER KEY.
+------------------------------------------------------------------+
: THE FOLLOWING PACKAGES ARE AVAILABLE: :
: 1 UXP@'SAMPLE SAMPLE PACKAGE' :
: (@'UXP/V) V10L20 X96121' :
: SELECT PACKAGE(S) YOU WISH TO PROCESS (OR 'ALL' TO PROCESS :
: ALL PACKAGES). (DEFAULT: ALL) : 'RET' :
+------------------------------------------------------------------+
<>:SQUARE BRACKET
IF THE PROMPT RETURNS, CHECK IF THE DIRECTORY NAMED UXP@'SAMPLE'
HAS BEEN GENERATED UNDER /VAR/SPOOL/PKG.
+------------------------------------------------------------------+
: # CD /VAR/SPOOL/PKG 'RET' :
: # LS 'RET' :
: UXP@'SAMPLE' :
+------------------------------------------------------------------+
AS SHOWN ABOVE, SEQUENTIALLY DEVELOP THE PACKAGES TO BE INSTALLED
WITH THE SPOOL DIRECTORY.
*6 IF THE INSTANCE NAME OF THE PACKAGE TO BE INSTALLED IS THE
SAME, EXECUTE THE PKGTRANS COMMAND WITH THE -N OPTION.
NOTE THE DEPENDENCE RELATION TO EXECUTE THE PKGTRANS COMMAND.
AFTER THE PKGTRANS COMMAND IS EXECUTED, THE DIRECTORY NAME IS
THE PACKAGE INSTANCE NAME WITH A NUMBER SUFFIXED. FOR EXAMPLE,
UXP@'SAMPLE', UXP@'SAMPLE.2', AND UXP@'SAMPLE.3', ... .
THE @'P'PKGADD COMMAND INSTALLS PACKAGES IN ASCENDING ORDER OF
THE DIRECTORY NAME. IN THIS EXAMPLE, THE ORDER IS
UXP@'SAMPLE', UXP@'SAMPLE.2', AND UXP@'SAMPLE.3', ...
NOTE THE DEPENDENCE RELATION TO CHECK THE ORDER OF THE
PACKAGES TO BE INSTALLED .
1
*7 IF PACKAGES WITH DEFFERENT PACKAGE INSTANCE NAMES HAVE THE
DEPENDENCE RELATION, INSTALL THE PACKAGES SEPARATELY.
(EXECUTE THE @'P'PKGADD AND @'I'PKGADD COMMANDS, THEN
REEXECUTE THESE COMMANDS FOR THE CORRESPONDING PACKAGES.)
EXAMPLE)
FIRST INSTALL UXP@'SAMPLE' THEN UXP@'PLF' WHEN UXP@'PLF'
DEPENDS ON UXP@'SAMPLE'.
IN THIS CASE, BE SURE TO EXECUTE THE PKGTRANS COMMAND.
A.1.4 INSTALLATION WORK PROCEDURE
1) CHANGE THE SYSTEM TO THE SINGLE USER MODE.
+------------------------------------------------------------------+
: # CD / 'RET' :
: # SHUTDOWN -G0 -Y 'RET' :
+------------------------------------------------------------------+
2) LOG IN THE SYSTEM WITH ROOT. EXECUTE THE @'P'PKGADD COMMAND AND
INSTALL THE PACKAGE IN PRIMARY @'PE'.
+------------------------------------------------------------------+
: # /SBIN/@'P'PKGADD 'RET' :
: PLEASE WAIT, MOUNTALL NOW... :
+------------------------------------------------------------------+
FIRST, THE MOUNTALL COMMAND IS EXECUTED. NEXT, SPECIFY THE DEVICE
WHEN THE FOLLOWING MESSAGES ARE DISPLAYED. THE (@'DAT') TAPE
DEVICE PACKAGE, THE SPOOL DIRECTORY OR DATA STREAM FORMAT PACKAGE
CAN BE SPECIFIED FOR THE DEVICE.
+------------------------------------------------------------------+
: PLEASE ENTER @'DEVICE :
: (DEFAULT /VAR/SPOOL/PKG): 'RET' :
+------------------------------------------------------------------+
<>:SQUARE BRACKET
WHEN THE SYSTEM INQUIRE THE DEVICE,ENTER THE FULL PATHNAME OF THE
SPOOL DIRECTORY THAT INSTALLS THE PACKAGE.
THE DEFAULT DEVICE IS /VAR/SPOOL/PKG.
THE MESSAGES BELOW ARE PRODUCT PACKAGE-SPECIFIC MESSAGES FOR EACH
PACKAGE. REFER TO THE SOFTWARE MANUALS , @'PTF'S, AND OTHER
APPLICATION HANDBOOKS OF EACH SOFTWARE PRODUCT FOR DETAILS ABOUT
THE FOLLOWING MESSAGES.
3) CHANGING THE SYSTEM TO THE MAINTENANCE @'IPL' GROUP.
*8 EXECUTE MAINTMODE -N FOR THE PACKAGE (FOR EXAMPLE, PRODUCT OF
THE LANGUAGE SYSTEM) INSTALLED IN STEP 2) THAT DOES NOT
REQUIRE THE SYSGEN COMMAND. IF EXECUTING THE MAINTMODE
COMMAND WITH THE -N OPTION SPECIFIED, THE RUN LEVEL OF THE
SYSTEM AUTOMATICALLY BECOMES 3.
HOWEVER, YOU CANNOT LOG IN THE SYSTEM WITHOUT THE @'OS'
CONSOLE.
1
+------------------------------------------------------------------+
: # /SBIN/MAINTMODE <-N> 'RET' :
+------------------------------------------------------------------+
<>:SQUARE BRACKET
WHEN EXECUTING THE MAINTMODE COMMAND WITHOUT ANY OPTION, SYSGEN
COMMAND AND NEWSYS COMMAND ARE EXECUTED IN THE MAINTMODE COMMAND.
RESTART THE SYSTEM BY INIT 3 AFTER THE SYSTEM IS REBOOTED BY THE
NEWSYS COMMAND.
4) INFLUENCE OF NON-SHARING OF IFCONFIGS FILE
IGNORE THE FOLLOWING MESSAGES DISPLAYED ON THE CONSOLE WHILE THE
SYSTEM IS CHANGED TO THE MAINTENANCE @'IPL' GROUP.
+------------------------------------------------------------------+
: @'UX':LANSTART: @'ERROR': LANC0: ADAPTER NOT DEFINED IN :
: /ETC/INET/IFCONFIGS:@'PEID=****' :
+------------------------------------------------------------------+
5) EXECUTE THE @'I'PKGADD COMMAND WITH ROOT AUTHORITY, AND INSTALL
THE PACKAGE IN THE SYSTEM DISK OF EACH @'IMPE'.
+------------------------------------------------------------------+
: # /SBIN/@'I'PKGADD 'RET' :
+------------------------------------------------------------------+
THE FOLLOWING MESSAGES ARE OUTPUT TO A STANDARD OUTPUT.
THE FOLLOWING IS AN EXAMPLE OF UXP@'SAMPLE' BEING INSTALLED IN THE
SYSTEM WHERE @'PEID' OF @'IMPE' IS SET AT 0004 AND 0008.
+------------------------------------------------------------------+
: *********************************************** :
: INSTALL START COPY UXP@'SAMPLE' TO PE0004 NOW :
: :
: UXP@'SAMPLE' :
: PE0004 :
: *********************************************** :
: COPY UXP@'SAMPLE' TO PE0004 NOW... :
: PKGADD START :
: : :
+------------------------------------------------------------------+
THE OPERATION RESUMES TO NORMAL PACKAGE INSTALLATION.
OPERATE THE SYSTEM ACCORDING TO THE DISPLAYED INSTRUCTIONS.
THE INSTALLATION IS SEQUENTIALLY EXECUTED AS FOLLOWS:
+------------------------------------------------------------------+
: *********************************************** :
: INSTALL START COPY UXP@'SAMPLE' TO PE0008 NOW :
: :
: UXP@'SAMPLE' :
: PE0008 :
: *********************************************** :
: COPY UXP@'SAMPLE' TO PE0008 NOW... :
: PKGADD START :
: : :
: : :
: : :
+------------------------------------------------------------------+
IGNORE THE FOLLOWING WARNING MESSAGE DISPLAYED WHEN THE @'I'PKGADD
COMMAND IS EXECUTED.
+------------------------------------------------------------------+
: @'WARNING': XXX FREE FILE NODES ARE NEEDED IN THE / FILESYSTEM, :
: BUT ONLY 4294967295 FILE NODES ARE CURRENTLY AVAILABLE. :
+------------------------------------------------------------------+
THE @'I'PKGADD EXECUTES THE PKGCHK COMMAND INTERNALLY. FOR THE
MESSAGE OUTPUT AS THE RESULT OF PLGCHK, REFER TO THE REFERENCE
MANUALS. ALSO, EXECUTE THE PKGINFO COMMAND AND FINALLY CONFIRM
THE APPLICATION.
6) RELEASE THE SETTING FOR THE MAINTENANCE @'IPL' GROUP.
EXECUTE THE MAINTMODE COMMAND WITH THE -R OPTION SPECIFIED TO
RELEASE THE SETTING FOR THE MAINTENANCE @'IPL' GROUP.
IF THE MAINTMODE COMMAND IS EXECUTED WITH THE -N OPTION SPECIFYING
CHANGE TO THE MAINTENANCE @'IPL' GROUP, THE FOLLOWING MESSAGES ARE
DISPLAYED AND PROCESSING AUTOMATICALLY SHUTS DOWN.
+------------------------------------------------------------------+
: # /SBIN/MAINTMODE -R 'RET' :
: RE-@'IPL', PLEASE. :
: :
: SHUTDOWN -G0 -Y :
+------------------------------------------------------------------+
@'IF' THE MAINTMODE COMMAND IS EXECUTED WITHOUT ANY OPTIONS
SPECIFYING CHANGE TO THE MAINTENANCE @'IPL' GROUP, THE FOLLOWING
MESSAGES ARE DISPLAYED AND PROCESSING AUTOMATICALLY SHUTS DOWN.
THE FOLLOWING IS AN EXAMPLE ON THE ASSUMPTION THAT @'PEID' OF
@'IMPE' IS SET AT 0004 AND 0008.
+------------------------------------------------------------------+
: # /SBIN/MAINTMODE -R 'RET' :
: CP /STAND/UNIX /MAINT/PE0004/STAND/NEW_UNIX :
: CP /STAND/UNIX /MAINT/PE0008/STAND/NEW_UNIX :
: ... :
: ... :
: :
: RE-@'IPL', PLEASE. :
: :
: SHUTDOWN -G0 -Y :
+------------------------------------------------------------------+
7) RESTART THE SYSTEM.
LOG IN THE SYSTEM WITH ROOT THEN CHANGE THE RUN LEVEL TO 3 BECAUSE
THE FOLLOWING MESSAGES ARE DISPLAYED. <@'PASSWORD'> PROMPTS THE
USER TO ENTER A ROOT PASSWORD.
THE PASSWORD IS NOT DISPLAYED ON THE SCREEN.
1
+------------------------------------------------------------------+
: @'INIT': NEW RUN LEVEL: @'S' 'RET' :
: :
: @'INIT: SINGLE USER MODE' :
: :
: TYPE CTRL-D TO PROCEED WITH NORMAL STARTUP, :
: (OR GIVE ROOT PASSWORD FOR SINGLE USER MODE): <@'PASSWORD'> 'RET':
: :
: # INIT 3 'RET' :
+------------------------------------------------------------------+
A.1.5 ACTIONS TO TAKE WHEN PROCESSING TERMINATES ABNORMALLY
1) WHEN THE @'P'PKGADD COMMAND TERMINATES ABNORMALLY
REFER TO SECTION A.4 IN THIS MANUAL AND REFERENCE MANUAL TO
RESOLVE THE ERROR. THEN REEXECUTE THE @'P'PKGADD COMMAND.
2) WHEN THE MAINTMODE COMMAND TERMINATES ABNORMALLY
A) WHEN MAINTMODE <-N> IS EXECUTED <>:SQUARE BRACKET
REFER TO SECTION A.4 IN THIS MANUAL AND REFERENCE MANUAL TO
RESOLVE THE ERROR. SHUTDOWN,THEN CHANGE THE RUN LEVEL TO 3.
THIS STARTS UP THE SYSTEM IN THE MAINTENANCE @'IPL' GROUP.
B) WHEN MAINTMODE -R IS EXECUTED
REFER TO SECTION A.4 IN THIS MANUAL AND REFERENCE MANUAL TO
RESOLVE THE ERROR. SHUTDOWN, THEN CHANGE THE RUN LEVEL TO 3.
THIS STARTS UP THE SYSTEM IN THE MAINTENANCE @'IPL' GROUP.
IF MAINTMODE -R CANNOT BE EXECUTED EVEN AFTER THE CAUSE OF ERROR
IS RESOLVED, CHANGE THE FILE NAMES AS FOLLOWS.(AT PRIMARY @'PE')
+------------------------------------------------------------------+
: # MV /ETC/MAINTMODE/BKUP/ETC/IPLTBL /ETC/IPLTBL 'RET' :
: # MV /ETC/MAINTMODE/BKUP/ETC/DFS/DFSTAB /ETC/DFS/DFSTAB 'RET' :
: # MV /ETC/MAINTMODE/BKUP/ETC/DEFAULT/LOGIN :
: /ETC/DEFAULT/LOGIN 'RET':
: # MV /ETC/MAINTMODE/BKUP/ETC/UFP/MAP /ETC/UFP/MAP 'RET' :
: # MV /ETC/MAINTMODE/BKUP/EXPORT/@'PE'X@'ROOT'/FHSWTAB :
: /EXPORT/@'PE'X@'ROOT'/FHSWTAB 'RET':
+------------------------------------------------------------------+
- IF /ETC/MAINTMODE/BKUP/ETC/UFP/MAP.OLT IS DEFINED:
+------------------------------------------------------------------+
: # MV /ETC/MAINTMODE/BKUP/ETC/UFP/MAP.OLT /ETC/UFP/MAP.OLT 'RET' :
+------------------------------------------------------------------+
RESTART THE SYSTEM AFTER THE CHANGES TO RESUME NORMAL OPERATION.
3) WHEN THE @'I'PKGADD COMMAND TERMINATES ABNORMALLY
REFER TO SECTION A.4 IN THIS MANUAL AND REFERENCE MANUAL TO
RESOLVE THE ERROR. THEN, REEXECUTE THE @'I'PKGADD COMMAND.
1
A.2 PROCEDURE FOR DELETING THE PACKAGE FROM THE TWO OR MORE @'IPL'
GROUP SYSTEM
THE FOLLOWING SECTION DESCRIBES THE PROCEDURE FOR DELETING THE
PACKAGE. NOTE THAT SOME OF THE PRODUCTS CANNOT BE DELETED.
FOR DELETING TWO OR MORE PACKAGE, REPEAT THE FOLLOWING 2) TO 5)
STEPS.
1) SET THE SYSTEM TO SINGLE USER MODE.
+------------------------------------------------------------------+
: # CD / 'RET' :
: # SHUTDOWN -G0 -Y 'RET' :
+------------------------------------------------------------------+
2) EXECUTE THE @'P'PKGRM COMMAND WITH ROOT AUTHORITY, AND DELETE THE
PACKAGE FROM THE PRIMARY @'PE'.
+------------------------------------------------------------------+
: # /SBIN/@'P'PKGRM 'RET' :
+------------------------------------------------------------------+
THE MESSAGE IN THE FOLLOWING EXAMPLE WILL BE DISPLAYED.
WHEN IT IS DISPLAYED, ENTER THE PACKAGE INSTANCE NAME TO BE
DELETED. IN THE FOLLOWING EXAMPLE, THE UXP@'SMPLE' IS TO BE
DELETED.
+------------------------------------------------------------------+
: ENTER PKGINSTANCE : UXP@'SAMPLE' 'RET' :
+------------------------------------------------------------------+
THE PROCEDURES AFTER THIS ARE THE SAME AS DELETING NORMAL
PACKAGE. FOLLOW THE INSTRUCTIONS ON THE SCREEN.
3) CHANGE THE SYSTEM TO THE MAINTENANCE @'IPL' GROUP.
+------------------------------------------------------------------+
: # /SBIN/MAINTMODE <-N> 'RET' :
+------------------------------------------------------------------+
<>:SQUARE BRACKET
WHEN EXECUTING THE MAINTMODE COMMAND WITHOUT ANY OPTION, SYSGEN
COMMAND AND NEWSYS COMMAND ARE EXECUTED AS WELL. RESTART THE
SYSTEM BY INIT 3 AFTER THE SYSTEM IS REBOOTED BY THE NEWSYS
COMMAND. LIKE THE PACKAGE APPLICATION, SPECIFICATION OF THE -N
OPTION OF SYSGEN COMMAND AND NEWSYS COMMAND IS UNNECESSARY.
4) EXECUTE THE @'I'PKGRM COMMAND WITH ROOT AUTHORITY, AND DELETE
THE PACKAGE FROM THE SYSTEM DISK OF EACH @'IMPE' (0004 IN THE
FOLLOWING EXAMPLE).
+------------------------------------------------------------------+
: *********************************************** :
: REMOVE START DELETE UXP@'SAMPLE' TO PE0004 NOW :
: UXP@'SAMPLE' :
: PE0004 :
: *********************************************** :
+------------------------------------------------------------------+
THE PROCEDURES FOLLOWING THIS ARE THE SAME AS THAT FOR DELETING
NORMAL PACKAGES. FOLLOW THE INSTRUCTIONS ON THE SCREEN.
1
5) CANCEL THE SETTING FOR THE MAINTENANCE @'IPL' GROUP.
+------------------------------------------------------------------+
: # /SBIN/MAINTMODE -R 'RET' :
+------------------------------------------------------------------+
A.3 PROCEDURE FOR INSUFFICIENT SPOOL AREA
A.3.1 PREFACE
FUJITSU RECOMMENDS THE FOLLOWING PROCEDURE TO INSTALL A LARGE
SOFTWARE PACKAGE IN TWO OR MORE @'IPL' GROUP SYSTEMS OPERATING
UNDER @'UXP/V V10L20':
(1) EXECUTE THE @'P'PKGADD COMMAND IN THE SINGLE USER MODE TO
INSTALL THE PACKAGE IN THE PRIMARY @'PE'.
(2) EXECUTE THE MAINTMODE COMMAND TO SWITCH THE SYSTEM TO THE
MAINTENANCE @'IPL' GROUP STATUS.
(3) EXECUTE THE @'I'PKGADD COMMAND IN THE MAINTENANCE @'IPL'
GROUP STATUS TO INSTALL THE PACKAGE IN THE SYSTEM DISK OF
EACH @'IMPE'.
(4) EXECUTE THE MAINTMODE COMMAND WITH THE -R OPTION SPECIFIED
TO SWITCH THE SYSTEM BACK TO THE SINGLE USER MODE.
IN THE MAINTENANCE @'IPL' GROUP STATUS, THE SYSTEM DISK OF EACH
@'IMPE' IS MOUNTED ON THE PRIMARY @'PE' AS AN @'NFS'. ONLY THE
PARTITIONS EXISTING BEFORE THE SYSTEM WAS INSTALLED ARE
AUTOMATICALLY MOUNTED AS AN @'NFS'. THIS OCCURS WHEN THE SYSTEM IS
SWITCHED TO THE MAINTENANCE @'IPL' GROUP.
THUS, THE SPOOL DIRECTORIES SPECIFIED WHEN THE @'P'PKGADD COMMAND
IS EXECUTED MAY NOT BE ON THE SYSTEM DISK OF EACH @'IMPE' DURING
THE SWITCH TO THE MAINTENANCE @'IPL' GROUP STATUS. THEREFORE, THE
@'I'PKGADD COMMAND USES /MAINT/PE"@'PEID'"/VAR/SPOOL/PKG AS THE
SPOOL DIRECTORY TO INSTALL THE PACKAGE IN EACH @'IMPE'.
ACCORDINGLY, IF A SOFTWARE PACKAGE THAT EXCEEDS THE SIZE OF THE
/VAR/SPOOL PARTITION IS INSTALLED, THE SPACE OF
/MAINT/PE"@'PEID'"/VAR/SPOOL WILL BE INSUFFICIENT AND AN
INSTALLATION FAILURE WILL RESULT.
THIS SECTION DESCRIBES HOW TO AVOID THIS SITUATION. NOTE THAT
INSTALLING A LARGE SOFTWARE PACKAGE REQUIRES MORE TIME THAN
INSTALLING ORDINARY SIZE PACKAGES.
1
A.3.2 OPERATION FLOW
EXECUTE THE FOLLOWING STEPS:
(1) PREPARE
(2) LOAD THE PACKAGE ON THE SPOOL DIRECTORY ON THE PRIMARY @'PE'.
(3) CHANGE TO THE SINGLE USER MODE AND EXECUTE THE MOUNTALL
COMMAND.
(4) INSTALL THE PACKAGE IN THE PRIMARY @'PE'.
(5) EXECUTE THE MAINTMODE COMMAND, AND CHANGE TO THE MAINTENANCE
@'IPL' GROUP.
(6) COPY THE PACKAGE LOADED IN STEP (3) ON EACH @'IMPE' SYSTEM
DISK.
(7) EXECUTE CHROOT IN THE MAINTENANCE @'IPL' GROUP TO INSTALL
THE PACKAGE IN EACH @'IMPE' SYSTEM DISK.
(8) EXECUTE MAINTMODE -R TO CHANGE TO THE SINGLE USER MODE.
(9) EXECUTE INIT 3 TO CHANGE TO THE REGULAR OPERATION MODE.
A.3.3 OPERATION PROCEDURE
1) SECURE A WORK AREA TO BE USED BY THE @'I'PKGADD COMMAND ON EACH
@'IMPE' SYSTEM DISK. (REFER TO A.7)
EDIT THE /EXPORT/@'PE"PEID"ROOT'/ETC/VFSTAB FILE IN THE PRIMARY
@'PE'.(@'PEID' REPRESENTS @'IMPE PEID' IN HEXADECIMAL NOTATION.)
WHEN CHANGING TO THE MAINTENANCE @'IPL' GROUP, REFERENCE THIS FILE
AND MOUNT EACH @'IMPE' SYSTEM DISK ON THE PRIMARY @'PE' AS AN
@'NFS'.
BELOW IS AN EXAMPLE OF /EXPORT/@'PE4ROOT'/ETC/VFSTAB WHEN
@'IMPE PEID' IS 4.
+------------------------------------------------------------------+
: #SPECIAL FSCKDEV :
: MOUNTP FSTYPE FSCKPASS AUTOMNT MNTOPTS :
: /PROC - :
: /PROC PROC - NO - :
: /DEV/FD - :
: /DEV/FD FD - NO - :
: /DEV/DSK/0004-0C4010S2 /DEV/RDSK/0004-0C4010S2 :
: /MAINT/PE0004 UFS 1 YES - :
: /DEV/DSK/0004-0C4010S4 /DEV/RDSK/0004-0C4010S4 :
: /MAINT/PE0004/STAND UFS 1 YES - :
: /DEV/DSK/0004-0C4010S5 /DEV/RDSK/0004-0C4010S5 :
: /MAINT/PE0004/USR UFS 1 YES - :
: /DEV/DSK/0004-0C4010S6 /DEV/RDSK/0004-0C4010S6 :
: /MAINT/PE0004/USR/SHARE UFS 1 YES - :
: /DEV/DSK/0004-0C4010S7 /DEV/RDSK/0004-0C4010S7 :
: /MAINT/PE0004/VAR UFS 1 YES - :
: /DEV/DSK/0004-0C4010S8 /DEV/RDSK/0004-0C4010S8 :
: /MAINT/PE0004/VAR/SADM UFS 1 YES - :
: /DEV/DSK/0004-0C4010S9 /DEV/RDSK/0004-0C4010S9 :
: /MAINT/PE0004/VAR/ADM UFS 1 YES - :
: /DEV/DSK/0004-0C4010S10 /DEV/RDSK/0004-0C4010S10 :
: /MAINT/PE0004/VAR/SPOOL UFS 1 YES - :
+------------------------------------------------------------------+
1
THE VFSTAB FILE DEFINES A PARTITION LARGER THAN THE PACKAGE TO BE
INSTALLED. IN THIS CASE, /VAR/DUMP IS USED AS A SPOOL.
AFTER EDITING, THE /EXPORT/@'PE4ROOT'/ETC/VFSTAB FILE IS AS FOLLOWS:
+------------------------------------------------------------------+
: #SPECIAL FSCKDEV :
: MOUNTP FSTYPE FSCKPASS AUTOMNT MNTOPTS :
: /PROC - :
: /PROC PROC - NO - :
: /DEV/FD - :
: /DEV/FD FD - NO - :
: /DEV/DSK/0004-0C4010S2 /DEV/RDSK/0004-0C4010S2 :
: /MAINT/PE0004 UFS 1 YES - :
: /DEV/DSK/0004-0C4010S4 /DEV/RDSK/0004-0C4010S4 :
: /MAINT/PE0004/STAND UFS 1 YES - :
: /DEV/DSK/0004-0C4010S5 /DEV/RDSK/0004-0C4010S5 :
: /MAINT/PE0004/USR UFS 1 YES - :
: /DEV/DSK/0004-0C4010S6 /DEV/RDSK/0004-0C4010S6 :
: /MAINT/PE0004/USR/SHARE UFS 1 YES - :
: /DEV/DSK/0004-0C4010S7 /DEV/RDSK/0004-0C4010S7 :
: /MAINT/PE0004/VAR UFS 1 YES - :
: /DEV/DSK/0004-0C4010S8 /DEV/RDSK/0004-0C4010S8 :
: /MAINT/PE0004/VAR/SADM UFS 1 YES - :
: /DEV/DSK/0004-0C4010S9 /DEV/RDSK/0004-0C4010S9 :
: /MAINT/PE0004/VAR/ADM UFS 1 YES - :
: /DEV/DSK/0004-0C4010S10 /DEV/RDSK/0004-0C4010S10 :
: /MAINT/PE0004/VAR/SPOOL UFS 1 YES - :
: /DEV/DSK/0004-0C4010S14 /DEV/RDSK/0004-0C4010S14 :
: /MAINT/PE0004/VAR/DUMP UFS - YES - :
+------------------------------------------------------------------+
THE SAME OPERATION IS EXECUTED FOR EACH @'IMPE' DEFINED IN THE
SYSTEM. THIS DEFINITION FILE IS ONLY USED ON THE MAINTENANCE @'IPL'
MODE. WE RECOMMENDS THAT THIS FILE BE RESTORED TO ITS ORIGINAL STATE
AFTER THE MAINTENANCE IS COMPLETED.
2) LOADING THE PACKAGE IN THE SPOOL DIRECTORY
+------------------------------------------------------------------+
: # PKGTRANS <@'DEVICE'> 'RET' :
+------------------------------------------------------------------+
<@'DEVICE'> MUST BE THE ADDRESS OF A TAPE DEVICE OR THE PATH OF THE
PACKAGE WITH A DATA STREAM FORMAT.
MUST BE A DIRECTORY IN THE PARTITION WITH MORE
SPACE THAN REQUIRED BY THE PACKAGE TO BE INSTALLED.
3) CHANGING TO THE SINGLE USER MODE
USE THE SHUTDOWN COMMAND TO CHANGE TO THE SINGLE USER MODE.
CHANGE TO THE SINGLE USER MODE AND EXECUTE THE MOUNTALL COMMAND.
THE FOLLOWING CODING THAT ENDS WITH THE LINE 'RET' REQUIRE THE USER
TO ENTER A ROOT PASSWORD WHEN PROMPTED WITH <@'PASSWORD'>.
THE PASSWORD IS NOT DISPLAYED ON THE SCREEN.
1
+------------------------------------------------------------------+
: # CD / 'RET' :
: # SHUTDOWN -G0 -Y 'RET' :
: : :
: @'INIT': NEW RUN LEVEL: @'S' 'RET' :
: :
: @'INIT': @'SINGLE USER MODE' :
: :
: TYPE CTRL-D TO PROCEED WITH NORMAL STARTUP, :
: (OR GIVE ROOT PASSWORD FOR SINGLE USER MODE): <@'PASSWORD'> 'RET':
: :
: # MOUNTALL 'RET' :
: # :
+------------------------------------------------------------------+
4) INSTALLING THE PACKAGE IN THE PRIMARY @'PE'
+------------------------------------------------------------------+
: # PKGADD -D -A <@'ADMINFILE'> 'RET' :
+------------------------------------------------------------------+
MUST BE THE DIRECTORY SPECIFIED IN STEP 2).
<@'ADMINFILE'> CAN BE ONE OF THE FOLLOWING CHARACTER STRINGS
DEPENDING ON THE TYPE OF PACKAGE TO BE INSTALLED:
@'PTF': UXPPTF
@'PUF': UXPPUF
@'PEF': UXPPEF
@'PLF': UXPPLF
MUST BE THE INSTANCE NAME OF THE PACKAGE TO BE INSTALLED.
5) EXECUTING THE MAINTMODE COMMAND TO CHANGE TO THE MAINTENANCE
@'IPL' GROUP
+------------------------------------------------------------------+
: # /SBIN/MAINTMODE <-N> 'RET' (*9) :
+------------------------------------------------------------------+
<>:SQUARE BRACKET
*9 WHEN THE PACKAGE INSTALLED IN STEP 4) DOES NOT REQUIRE SYSGEN
(E.G. A PROGRAMMING LANGUAGE PRODUCT), EXECUTE MAINTMODE -N.
THE -N OPTION AUTOMATICALLY SETS THE RUN LEVEL TO 3.
HOWEVER, YOU CANNOT LOG IN THE SYSTEM WITHOUT THE @'OS' CONSOLE.
6) COPYING THE PACKAGE LOADED IN STEP 2) ONTO EACH @'IMPE' SYSTEM
DISK
SPECIFY /MAINT/PE"@'PEID'"/VAR/DUMP IN THE SPOOL DIRECTORY USED TO
INSTALL THE @'IMPE' PACKAGE BECAUSE /VAR/DUMP WAS ADDED TO THE
/EXPORT/@'PE"PEID"ROOT'/ETC/VFSTAB FILE IN STEP 1).
+------------------------------------------------------------------+
: # CP -RP / :
: /MAINT/PE"@'PEID'"/VAR/DUMP 'RET':
+------------------------------------------------------------------+
MUST BE THE ONE SPECIFIED IN STEPS 2) AND 4).
MUST BE THE INSTANCE NAME OF THE PACKAGE TO BE INSTALLED.
1
AN EXAMPLE OF COPY OF THE PACKAGE LOADED IN /VAR/SPOOL/PKG ON THE
PRIMARY @'PE' WITH A DIRECTORY FORMAT ONTO THE @'IMPE(PEID':0004)
SYSTEM DISK.
+------------------------------------------------------------------+
: # CP -RP /VAR/SPOOL/PKG/UXP@'SAMPLE' /MAINT/PE0004/VAR/DUMP 'RET':
+------------------------------------------------------------------+
EXECUTE THE ABOVE OPERATION FOR EACH @'IMPE'.
7) EXECUTING CHROOT IN THE MAINTENANCE @'IPL' GROUP TO INSTALL THE
PACKAGE
+------------------------------------------------------------------+
: # CHROOT /MAINT/PE"@'PEID'" /USR/SBIN/PKGADD -D :
: <@'IMPE'-SPOOL-DIRECTORY> -A <@'ADMINFILE'> 'RET':
+------------------------------------------------------------------+
AN INSTALLATION EXAMPLE OF UXP@'SAMPLE (PTF)' IN THE @'IMPE'
(@'PEID':0004) SYSTEM DISK WHICH WAS COPIED INTO /VAR/DUMP IN STEP
6):
+------------------------------------------------------------------+
: # CHROOT /MAINT/PE0004 /USR/SBIN/PKGADD -D /VAR/DUMP :
: -A UXPPTF UXP@'SAMPLE' 'RET' :
+------------------------------------------------------------------+
CHECK THAT THE APPLICATION IS WORKING CORRECTLY.
+------------------------------------------------------------------+
: # CHROOT /MAINT/PE0004 /USR/SBIN/PKGCHK -N UXP@'SAMPLE' 'RET' :
: # NO PROBLEM IF NOTHING IS DISPLAYED. :
+------------------------------------------------------------------+
EXECUTE THE ABOVE OPERATION FOR EACH @'IMPE'.
8) EXECUTE THE MAINTMODE -R AND CANCEL THE SETTING FOR THE
MAINTENANCE @'IPL' GROUP.
+------------------------------------------------------------------+
: # /SBIN/MAINTMODE -R 'RET' :
+------------------------------------------------------------------+
9) EXECUTING INIT 3 TO CHANGE TO THE REGULAR OPERATION MODE
+------------------------------------------------------------------+
: # INIT 3 'RET' :
+------------------------------------------------------------------+
10) APPLICATION CONFIRMATION
EXECUTE THE PKGINFO COMMAND ON EACH @'IMPE' AND VERIFY THAT THE
APPLICATION IS WORKING CORRECTLY.
1
A.4 ERROR MESSAGE COLLECTION
<@'PKG2'DIRECTORY>
+---------------------------------------------------------------------+
: @'PKG2'DIRECTORY: @'ERROR': BAD FORMAT, THIS FILE IS NOT @'PKG' :
: CAUSE: THE SPECIFIED FILE IS NOT A PACKAGE WITH A DATA STREAM :
: FORMAT. :
: ACTION: CONFIRM THE SPECIFIED FILE. :
+---------------------------------------------------------------------+
: @'PKG2'DIRECTORY: @'ERROR': PKGTRANS FAILD :
: CAUSE: THE PROGRAM FAILED IN PKGTRANS. :
: ACTION: INVESTIGATE THE CAUSE OF THE PKGTRANS FAILURE AND REEXECUTE.:
+---------------------------------------------------------------------+
: @'PKG2'DIRECTORY: @'ERROR': CHECK "@'DEVICE'" OK? :
: CAUSE: THE PROGRAM FAILED TO REWIND THE SPECIFIED TAPE DEVICE. :
: ACTION: CONFIRM THE DEVICE SPECIFIED IS A CORRECT TAPE DEVICE. :
+---------------------------------------------------------------------+
: @'PKG2'DIRECTORY: @'ERROR': "@'DEVICE'" PKGTRANS FAILED :
: CAUSE: THE PROGRAM FAILED IN PKGTRANS FROM THE SPECIFIED TAPE :
: DEVICE. :
: ACTION: INVESTIGATE THE CAUSE OF THE PKGTRANS FAILURE AND REEXECUTE.:
+---------------------------------------------------------------------+
: @'PKG2'DIRECTORY: @'ERROR': DEVICE DOES NOT HAVE @'PKG' :
: CAUSE: THE PACKAGE DOES NOT EXIST IN THE SPECIFIED DEVICE. :
: ACTION: CONFIRM THAT THE CORRECT DEVICE IS SPECIFIED. :
+---------------------------------------------------------------------+
+---------------------------------------------------------------------+
: CHECK_HISTFILE: ERROR: /VAR/SPOOL/PKG/.HISTORY CAN NOT OPEN :
: CAUSE: THE /VAR/SPOOL/PKG/.HISTORY FILE DOES NOT EXIST. :
: ACTION: CHECK THE CURRENT SYSTEM STATUS TO DETERMINE WHETHER THE :
: PACKAGES INSTALLED IN THE SYSTEM DISK FOR THE PRIMARY @'PE' :
: AND @'IMPE'S HAVE THE SAME VERSION AND LEVEL. :
: IF NOT, CORRECT THE VERSION AND LEVEL. :
+---------------------------------------------------------------------+
: CHECK_HISTFILE: ERROR: BAD PKGINSTANCE "@'PKGINSTANCE'" OR :
: BAT FORMAT /VAR/SPOOL/PKG/.HISTORY FILE :
: CAUSE: THE PACKAGE INSTANCE SPECIFIED CONTAINS MISTAKES OR THE :
: CONTENT OF THE /VAR/SPOOL/PKG/.HISTORY FILE CONTAINS :
: CONTRADICTIONS. :
: ACTION: CONFIRM THE PACKAGE INSTANCE NAME. :
: CHECK THE CURRENT SYSTEM STATUS TO DETERMAINE WHETHER THE :
: PACKAGES INSTALLED IN THE SYSTEM DISKS FOR THE PRIMARY @'PE':
: AND @'IMPE'S HAVE THE SAME VERSION AND LEVEL. :
: IF NOT, CORRECT THE VERSION AND LEVEL. :
+---------------------------------------------------------------------+
1
+---------------------------------------------------------------------+
: MKHISTFILE: @'ERROR': "@'SPOOLTMP'" HAS NOT @'PKG' :
: CAUSE: THE PACKAGE WITH A DIRECTORY FORMAT DOES NOT EXIST IN THE :
: SPOOL DIRECTORY. :
: ACTION: CONFIRM THAT THE PACKAGE WITH A DIRECTORY FORMAT EXISTS :
: UNDER THE "@'SPOOLTMP'"CONTROL. :
+---------------------------------------------------------------------+
: MKHISTFILE: ERROR: CAN NOT FIND /ETC/IPLTBL.MAINT :
: CAUSE: /ETC/IPLTBL.MAINT COULD NOT BE FOUND. :
: ACTION: MATCH THE /ETC/IPLTBL.MAINT FILE TO THE SYSTEM :
: CONFIGURATION. :
+---------------------------------------------------------------------+
: MKHISTFILE: ERROR: "@'SPOOLTMP'" DOES NOT HAVE "@'PKGINSTANCE'" :
: CAUSE: THE PACKAGE OF "@'PKGINSTANCE'" DOES NOT EXIST IN THE SPOOL :
: DIRECTORY. :
: ACTION: CONFIRM THAT "@'PKGINSTANCE'" EXISTS UNDER THE "@'SPOOLTMP'":
: CONTROL. :
+---------------------------------------------------------------------+
: MKHISTFILE: ERROR: "@'PKGINSTANCE'" IS NOT INSTALLED :
: CAUSE: "@'PKGINSTANCE'" IS NOT INSTALLED IN THE SYSTEM. :
: ACTION: CONFIRM THAT THE SPECIFIED PACKAGE INSTANCE IS CORRECT. :
+---------------------------------------------------------------------+
A.5 HOW TO CREATE /ETC/IPLTBL.MAINT AND
/EXPORT/@'PE'X@'ROOT'/FHSWTAB.MAINT
A.5.1 HOW TO CREATE /ETC/IPLTBL.MAINT
CREATE THE ENTRY OF /ETC/IPLTBL ONLY FOR THE PRIMARY @'PE' AND
@'IMPE'. REWRITE @'IMPE' WITH @'SIOPE'.
ALSO REWRITE BOOT_DEV AND PART AS FOLLOWS:
+------------------------------------------------------------------+
: # :
: #@'IPL'G @'PCG PPID PE'TYPE @'PEID' STYPE STATUS ALT_STATUS :
: BOOT_DEV PART :
: # :
: # @'IPL' GROUP 0 :
: 0000 0000 0000 @'P_PE' 0000 -- @'UP' -- :
: -- 0 :
: # @'IPL' GROUP 1 :
: 0001 0000 0001 @'S_PE' 0001 -- @'UP' -- :
: -- 0 :
: 0001 0000 0002 @'IMPE' 0002 -- @'UP' -- :
: 0C4010 2 :
: # @'IPL' GROUP 2 :
: 0002 0000 0004 @'IMPE' 0004 -- @'UP' -- :
: 0C4010 2 :
: .... .... .... .... .... .. .. .. :
: ...... . :
+------------------------------------------------------------------+
1
+------------------------------------------------------------------+
: # :
: #@'IPL'G @'PCG PPID PE'TYPE @'PEID' STYPE STATUS ALT_STATUS :
: BOOT_DEV PART :
: # :
: # @'IPL' GROUP 0 :
: 0000 0000 0000 @'P_PE' 0000 -- @'UP' -- :
: -- 0 :
: 0001 0000 0002 @'SIOPE' 0002 -- @'UP' -- :
: -- 0 :
: 0002 0000 0004 @'SIOPE' 0004 -- @'UP' -- :
: -- 0 :
: .... .... .... .... .... .. .. .. :
: .. . :
+------------------------------------------------------------------+
DESCRIBE ONLY THE PRIMARY @'PE' AND @'SIOPE' IN IPLTBL.MAINT.
A.5.2 HOW TO CREATE /EXPORT/@'PE'X@'ROOT'/FHSWTAB.MAINT
EXECUTE THE FOLLOWING COMMANDS.
IN THE FOLLOWING EXAMPLE, @'PEID' IS 0004 AND @'PE' WITH @'ID'
0008 IS @'IMPE'.
+------------------------------------------------------------------+
: # /USR/UXPLIB/SETUP/BIN/MK_FHSWTAB 4 8 > :
: /EXPORT/@'PE'X@'ROOT'/FHSWTAB.MAINT 'RET' :
+------------------------------------------------------------------+
A.6 NOTES FOR INSTALLING MULTIPLE @'IMPE'S PACKAGE
1) EXECUTING THE @'P'PKGADD -P COMMAND
IF @'N' IS THE RESPONSE TO THE QUESTION ISSUED BY THE PACKAGE
SCRIPT AND IF THE INSTALLATION STOPS WHEN EXECUTING THE @'P'PKGADD
-P COMMAND, DELETE THE FOLLOWING FILE:
THE -P OPTION IS FOR APPLYING THE PACKAGE TO EACH @'IMPE' IN
PARALLEL.
/VAR/SPOOL/PKG/HISTORY.ADD
2) EXECUTING THE @'I'PKGADD -P COMMAND
IF A RESPONSE IS NOT RECEIVED WITHIN 15 MINUTES OF EXECUTING THE
@'I'PKGADD -P COMMAND, TEMPORARILY STOP THE INSTALLATION.
THEN INSTALL THE PACKAGE IN THE SERIAL OPERATION (EXECUTE
@'I'PKGADD WITHOUT OPTIONS).
THE -P OPTION IS FOR APPLYING THE PACKAGE TO EACH @'IMPE' IN
PARALLEL.
1
+------------------------------------------------------------------+
: # @'I'PKGADD -P '@'RET' :
: :
: CHECK INSTALL _ENVIRONMENT NOW :
: COMPLETE :
: :
: ------------------------------ :
: COPING PKGDATA(UXP@'SAMPLE') NOW :
: COMPLETE :
: :
: PARALLEL INSTALL(UXP@'SAMPLE') NOW <--IF A RESPONSE IS NOT :
: RECEIVED WITHIN 15 MINUTES OF :
: THIS MESSAGE :
+------------------------------------------------------------------+
3) IF THE FOLLOWING MESSAGES ARE DISPLAYED WHEN THE @'I'PKGADD
COMMAND WITHOUT OPTIONS IS EXECUTED (THE PACKAGE IS INSTALLED IN
SERIAL OPERATION), REINSTALL THE PACKAGE IN THE PRIMARY @'PE'
WITH THE MAINTENANCE @'IPL' GROUP UNCHANGED.
THEN, EXECUTE THE @'I'PKGADD COMMAND.
+------------------------------------------------------------------+
: INSTALLATION OF WAS SUCCESSFULL. :
: @'ERROR': /ETC/RC2.D/@'SXX'XXXX :
: PATHNAME DOES NOT EXIST :
+------------------------------------------------------------------+
A.7 PROCEDURE OF AND NOTES ON EXTENDING /VAR/SADM/PKG AREA
A.7.1 INCREASE OF MINI DISK
1) UPDATE THE @'VTOC' INFORMATION ON @'P-PE' AND @'IMPE'
+------------------------------------------------------------------+
: # PRTVTOC -F AAA /DEV/RDSK/0000-0C4010S0 'RET' :
: # VI AAA 'RET' ==> EDIT :
: # EDVTOC -O -F AAA /DEV/RDSK/0000-0C4010S0 'RET' :
: THE ABOVE-MENTIONED OPERATION IS EXECUTED BY @'P-PE' AND EACH :
: @'IMPE'. :
+------------------------------------------------------------------+
REBOOT THE SYSTEM.
+------------------------------------------------------------------+
: # SHUTDOWN -G0 -Y -I6 'RET' :
+------------------------------------------------------------------+
THEN, DO FOLLOWING PROCEDURE.
1
+------------------------------------------------------------------+
: # MKFS -@'F' UFS /DEV/RDSK/0000-@'XXXXXX'S@'X' NNNNN 'RET' :
: # MOUNT -@'F' UFS /DEV/DSK/0000-@'XXXXXX'S@'X' /MNT 'RET' :
: # CD /VAR/SADM/PKG 'RET' :
: # FIND . -DEPTH -PRINT ? CPIO -PDMU /MNT 'RET' ?:PIPE :
: # CD / 'RET' :
: # DIRCMP /VAR/SADM/PKG /MNT 'RET' ==> CONFIRMS UNDER THE /MNT :
: # /BIN/RM -FR /VAR/SADM/PKG 'RET' :
: # UMOUNT /MNT 'RET' :
: # MKDIR /VAR/SADM/PKG 'RET' :
: # MOUNT -@'F' UFS /DEV/DSK/0000-@'XXXXXX'S@'X' /VAR/SADM/PKG 'RET'
: # /SBIN/DF 'RET' ==> IT IS CONFIRMED TO BE INCREASED. :
: THE ABOVE-MENTIONED OPERATION IS EXECUTED BY @'P-PE' AND EACH :
: @'IMPE'. :
+------------------------------------------------------------------+
NOTE: @'XXXXXX'S@'X' IS AN ADDRESS ON THE INCREASE MINI DISK, AND
THE NNNNN INDICATES THE SIZE OF INCREASE.
2) EDIT OF ENVIRONMENTAL FILE
- EDIT /ETC/VFSTAB AND /ETC/UFP/MAP ON @'P-PE' AND EACH @'IMPE'
AND ADD THE ENTRY OF /VAR/SADM/PKG.
A.7.2 THE PROCEDURE THAT INCREASE DISK CAN BE USED AT MAINTENANCE
@'IPL' MODE.
- EDIT /EXPORT/@'PE"PEID"ROOT'/ETC/VFSTAB, AND ADD THE ENTRY OF
/VAR/SADM/PKG.
A.7.3 NOTES
- IT IS NECESSARY TO CONFIRM THAT THE INCREASED SPACE CAN BE
REFERENCE CORRECTLY (AT OPERATION USUALLY/AT MAINTENANCE @'IPL'
MODE).
- EXECUTE THE "/BIN/DF" COMMAND WHEN THE SYSTEM IS OPERATION
USUALLY AND MAINTENANCE @'IPL' MODE.
CHECK THE OUTPUT RESULT OF THE "/BIN/DF" COMMAND, AND CONFIRM
THE INCREASED DISK SPACE CAN BE REFERENCE CORRECTLY FROM
@'P-PE' AND EACH @'IMPE'.
- CONFIRM CAN THE CORRECT REFERENCE TO INFORMATION BY EXECUTING
THE PKGINFO COMMAND TO EACH @'IMPE' AT MAINTENANCE @'IPL' MODE.
1
+-------------------+----------------+
: MANAGEMENT NUMBER : @'HUXV-00073 :
+---------------------+----------+-------+-----------+----------------+
:OPERATING SYSTEM, :BEFORE CONVERSION : @'UXP/V UXP/V V10L20' :
:PRODUCT NAME, : : @'X97061' :
:EDITION OR VERSION +------------------+----------------------------+
:AND LEVEL, :AFTER CONVERSION : @'UXP/V UXP/V V10L20' :
:AND @'PTF' : : @'X97091' :
+--------------+------+---------------+--+-------+--------------------+
:FUNCTION : STORAGE CONTROL :INDIVIDUAL:@'BKRS' :
: GROUP : : FUNCTION : :
+--------------+----------------------+----------+--------------------+
:INCOMPATIBLE : MODIFICATION OF THE @'PE' NUMBER AS SPECIFIED BY :
: FUNCTION : @'BKRS' :
+--------------+------------------------------------------------------+
:CONDITIONS : WHEN ACCESSING A @'PE' RESOURCE (FILE SYSTEM, DISK, :
:(PRODUCT : AND TAPE) IN WHICH THE @'PE' NUMBER SPECIFIED BY :
:COMBINATIONS) : @'BKRS' IS 0X@'A' OR MORE :
+--------------+------------------------------------------------------+
:REASON : 1. ADDED FUNCTION 2. IMPROVED FUNCTION :
: : 3. IMPROVED PERFORMANCE 4. IMPROVED CHECK FUNCTION :
: :*5. CORRECTED FAILURE 6. MODIFIED FUNCTION SYSTEM :
: : 7. ( ) :
+--------------+------------------------------------------------------+
:ACTION TO BE : 1. @'JCL' STATEMENT MODIFICATION :
: TAKEN : 2. CONTROL DATA MODIFICATION :
: : 3. SOURCE PROGRAM MODIFICATION 4. RECOMPILATION :
: : 5. RELINKAGE EDITION *6. FILE MODIFICATION :
: : 7. SYSTEM PARAMETER MODIFICATION :
: :*8. OPERATOR EXPERIENCE 9. ( ):
+--------------+------------------------------------------------------+
:RESPONSIBILITY:*1. SYSTEM MANAGER 2. SYSTEM PROGRAMMER :
: : 3. PROGRAMMER 4. CENTER OPERATOR :
: : 5. END USER 6. ( ):
+--------------+---------------------------------------+--------------+
:RESULT IF NO :*1. RESOURCE DAMAGE :ERROR MESSAGE :
: ACTION TAKEN :*2. PROCESSING RESULT INCORRECT :AND COMPLETION:
: :*3. ABNORMAL TERMINATION :CODE :
: : 4. ACTIVATION DISABLED : :
: : 5. CHANGE IN RESOURCE AND PERFORMANCE : :
: : 6. OTHER CHANGE DETECTED : :
+--------------+---------------------------------------+--------------+
: CONVERT THE @'PE' NUMBER AS SPECIFIED BY @'BKRS'
FROM A DECIMAL NUMBER TO A HEXADECIMAL NUMBER.
-----------------------------------------------------------------------
: WHEN SPECIFYING @'PE' NUMBER TO THE SAVING
BACKUP OPERATION TABLE.
: SPECIFIES A DECIMAL NUMBER FOR THE @'PE' NUMBER.
: SPECIFIES A HEXADECIMAL NUMBER FOR THE @'PE'
NUMBER.
: CONVERT THE @'PE' NUMBER IN THE SAVING OPERATION
TABLE TO A HEXADECIMAL NUMBER BY ISSUING A
BKRSMENU(1@'M') COMMAND.
-----------------------------------------------------------------------
1
: WHEN RESTORING THE DATA SAVED BEFORE @'X97061'
WITHOUT SPECIFYING .
: THE DATA IS RESTORED TO THE @'PE' SPECIFIED AT
SAVING.
: WHEN THE @'PE' NUMBER SPECIFIED BEFORE SAVING IS
0X@'A' OR MORE, IT IS RESTORED TO A @'PE' OTHER
THAN THE @'PE' TO BE ABNORMALLY TERMINATED OR
RESTORED.
: SPECIFY THE @'PE' NUMBER STORED IN HISTORY
INFORMATION TO THE <@'PE' AT SAVING> AND SPECIFY
THE DESTINATION @'PE' NUMBER OF RESTORATION TO
BY HEXADECIMAL.
-----------------------------------------------------------------------
(DETAILED INFORMATION: NONE)
1
+-------------------+----------------+
: MANAGEMENT NUMBER : @'HUXV-00074' :
+---------------------+----------+-------+-----------+----------------+
:OPERATING SYSTEM, :BEFORE CONVERSION : @'UXP/V UXP/V V10L20' :
:PRODUCT NAME, : : @'X98031' :
:EDITION OR VERSION +------------------+----------------------------+
:AND LEVEL, :AFTER CONVERSION : @'UXP/V UXP/V V10L20' :
:AND @'PTF' : : @'X98061' :
+--------------+------+--------------+---+-------+--------------------+
:FUNCTION : @'MAIL' :INDIVIDUAL : SENDMAIL COMMAND :
: GROUP : : FUNCTION : :
+--------------+---------------------+-----------+--------------------+
:INCOMPATIBLE : MODIFICATION OF MAIL SENDING AND RECEIVING PROCESSING:
: FUNCTION : :
+--------------+------------------------------------------------------+
:CONDITIONS : SENDING AND RECEIVING MAIL TO A USER WITH A .FORWARD :
:(PRODUCT : FILE UNDER A HOME DIRECTORY :
:COMBINATIONS) : :
+--------------+------------------------------------------------------+
:REASON : 1. ADDED FUNCTION 2. IMPROVED FUNCTION :
: : 3. IMPROVED PERFORMANCE*4. IMPROVED CHECK FUNCTION :
: :*5. CORRECTED FAILURE 6. MODIFIED FUNCTION SYSTEM :
: : 7. ( ) :
+--------------+------------------------------------------------------+
:ACTION TO BE : 1. @'JCL' STATEMENT MODIFICATION :
: TAKEN : 2. CONTROL DATA MODIFICATION :
: : 3. SOURCE PROGRAM MODIFICATION 4. RECOMPILATION :
: : 5. RELINKAGE EDITION 6. FILE MODIFICATION :
: : 7. SYSTEM PARAMETER MODIFICATION :
: : 8. OPERATOR EXPERIENCE :
: :*9.(MODIFICATION OF FILE PERMISSION) :
+--------------+------------------------------------------------------+
:RESPONSIBILITY:*1. SYSTEM MANAGER 2. SYSTEM PROGRAMMER :
: : 3. PROGRAMMER 4. CENTER OPERATOR :
: :*5. END USER 6. ( ):
+--------------+---------------------------------------+--------------+
:RESULT IF NO : 1. RESOURCE DAMAGE :ERROR MESSAGE :
: ACTION TAKEN :*2. PROCESSING RESULT INCORRECT :AND COMPLETION:
: : 3. ABNORMAL TERMINATION :CODE :
: : 4. ACTIVATION DISABLED : :
: : 5. CHANGE IN RESOURCE AND PERFORMANCE : :
: : 6. OTHER CHANGE DETECTED : :
+--------------+---------------------------------------+--------------+
: CHANGING THE PROCESSING OF SENDING AND RECEIVING
MAIL TO A USER WITH A .FORWARD FILE UNDER A HOME
DIRECTORY
-----------------------------------------------------------------------
: WHEN SENDING MAIL TO A USER AS INDICATED BELOW
BY A SENDMAIL COMMAND:
- A USER WITH A .FORWARD FILE WHICH CAN ALSO
BE WROTE BY OTHER USERS AND CONTAINS COMMAND
SPECIFICATIONS.
: (SENDING SIDE)
SUCCEED IN SENDING MAIL.
(RECEIVING SIDE)
ABLE TO EXECUTE COMMANDS.
1
: (SENDING SIDE)
A ERROR MAIL IS RETURNED.
THE ERROR MESSAGE OF THE ERROR MAIL IS AS
FOLLOWS: 550 (HOME DIRECTORY)/.FORWARD: LINE
(LINE NUMBER): COMMAND ... ADDRESS(MAIL ADDRESS)
IS UNSAFE FOR MAILING TO PROGRAMS.
(RECEIVING SIDE)
NOT ABLE TO EXECUTE COMMANDS.
: IF THE USER SATISFIES THE FOLLOWING CONDITIONS,
CHANGE THE CONDITIONS SO THAT THE OTHER USERS
ARE NOT PERMITTED TO WRITE A .FORWARD FILE:
- A USER HAS A .FORWARD FILE UNDER A HOME
DIRECTORY. AND
- USERS OTHER THAN THE OWNER OF A .FORWARD
FILE HAVE WRITE PERMISSION. AND
- THE .FORWARD FILE CONTAINS COMMAND
SPECIFICATIONS.
-----------------------------------------------------------------------
(DETAILED INFORMATION: NONE)
1
+-------------------+----------------+
: MANAGEMENT NUMBER : @'HUXV-00075' :
+---------------------+----------+-------+-----------+----------------+
:OPERATING SYSTEM, :BEFORE CONVERSION : @'UXP/V UXP/V V10L20' :
:PRODUCT NAME, : : @'X98031' :
:EDITION OR VERSION +------------------+----------------------------+
:AND LEVEL, :AFTER CONVERSION : @'UXP/V UXP/V V10L20' :
:AND @'PTF' : : @'X98061' :
+--------------+------+--------------+---+-------+--------------------+
:FUNCTION : @'MAIL' :INDIVIDUAL : SENDMAIL COMMAND :
: GROUP : : FUNCTION : :
+--------------+---------------------+-----------+--------------------+
:INCOMPATIBLE : ENHANCEMENT OF CHECKING THE HARD LINK FILE BY MAIL :
: FUNCTION : (FACILITY) :
+--------------+------------------------------------------------------+
:CONDITIONS : SENDING AND RECEIVING MAIL TO A USER OR ALIAS NAME :
:(PRODUCT : WITH A .FORWARD FILE UNDER A HOME DIRECTORY :
:COMBINATIONS) : :
+--------------+------------------------------------------------------+
:REASON : 1. ADDED FUNCTION 2. IMPROVED FUNCTION :
: : 3. IMPROVED PERFORMANCE*4. IMPROVED CHECK FUNCTION :
: :*5. CORRECTED FAILURE 6. MODIFIED FUNCTION SYSTEM :
: : 7. ( ) :
+--------------+------------------------------------------------------+
:ACTION TO BE : 1. @'JCL' STATEMENT MODIFICATION :
: TAKEN : 2. CONTROL DATA MODIFICATION :
: : 3. SOURCE PROGRAM MODIFICATION 4. RECOMPILATION :
: : 5. RELINKAGE EDITION 6. FILE MODIFICATION :
: : 7. SYSTEM PARAMETER MODIFICATION :
: : 8. OPERATOR EXPERIENCE :
: :*9.(MODIFICATION OF FILE PERMISSION) :
+--------------+------------------------------------------------------+
:RESPONSIBILITY:*1. SYSTEM MANAGER 2. SYSTEM PROGRAMMER :
: : 3. PROGRAMMER 4. CENTER OPERATOR :
: :*5. END USER 6. ( ):
+--------------+---------------------------------------+--------------+
:RESULT IF NO : 1. RESOURCE DAMAGE :ERROR MESSAGE :
: ACTION TAKEN :*2. PROCESSING RESULT INCORRECT :AND COMPLETION:
: : 3. ABNORMAL TERMINATION :CODE :
: : 4. ACTIVATION DISABLED : :
: : 5. CHANGE IN RESOURCE AND PERFORMANCE : :
: : 6. OTHER CHANGE DETECTED : :
+--------------+---------------------------------------+--------------+
: CHECKING WHETHER A .FORWARD FILE TO WHICH MAIL IS
DELIVERED AND AN ALIAS DEFINITION FILE SPECIFIED
BY :INCLUDE: IS A HARD LINK FILE.
-----------------------------------------------------------------------
: WHEN SENDING MAIL TO A USER AS INDICATED BELOW
USING A SENDMAIL COMMAND:
- A USER WITH A HARD LINK .FORWARD FILE.
: MAIL IS DELIVERED AS INSTRUCTED BY A .FORWARD
FILE.
: MAIL IS DELIVERED TO THE DESTINATION ADDRESS.
-----------------------------------------------------------------------
1
: WHEN SENDING MAIL TO A USER AS INDICATED BELOW
USING A SENDMAIL COMMAND:
- AN ALIAS WITH A DEFINITION CONTAINING :INCLUDE:
SPECIFICATION AND A HARD LINK FILE.
: MAIL IS DELIVERED AS INSTRUCTED BY THE ALIAS
DEFINITION.
: A ERROR MAIL IS RETURNED TO THE SENDER.
THE ERROR MESSAGE OF A ERROR MAIL IS THE
FOLLOWING:
550 :INCLUDE: (FILE) ... CANNOT OPEN (FILE):
OPERATION NOT PERMITTED.
: WHEN THE USER HAS A .FORWARD FILE UNDER A HOME
DIRECTORY, AND WHEN THE FILE IS A HARD LINK FILE,
TERMINATE THE HARD LINK.
WHEN THE USER HAS A FILE SPECIFIED BY :INCLUDE:
OF THE ALIAS DEFINITION, AND WHEN THE FILE IS A
HARD LINK, TERMINATE THE HARD LINK.
-----------------------------------------------------------------------
(DETAILED INFORMATION: NONE)
1 PROGRAM TEMPORARY FIX REPORT PAGE 0001
*-----------------------------------------------------------------*
! SYSTEM NAME ! PRODUCT ID ! PRODUCT VL ! PTF NAME ! PAST PTFS !
*-----------------------------------------------------------------*
! UXP/V ! UXP/V ! V10L20 ! X98061 ! 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 UX12969 P112145 IOS 1 1
0002 UX13248 P123273 ELOG 1 1
0003 UX13846 P775008 LP 1 1
0004 UX14123 P774443 PXJOBSWAP 1 1
0005 UX14183 P775010 HIP 1 1
0006 UX14210 P775079 CRON 1 1
0007 UX14216 P121620 MAIL 1 1
0008 UX14218 P121624 MAIL 1 1
0009 UX14220 P122000 MAIL 1 1
0010 UX14222 P122001 MAIL 1 1
0011 UX14244 P775028 FDDI 1 1
0012 UX14245 P122454 FDDI 5 1
0013 UX14246 P122502 JOBFRZ 1 1
0014 UX14251 P774997 USRENV 1 1
0015 UX14256 P775134 IOS 1 1
0016 UX14261 P122417 NFS 1 1
0017 UX14262 P122503 NFS 1 1
0018 UX14265 P774904 FORKEXEC 1 1
0019 UX14267 P122629 FS 1 1
0020 UX14268 P122634 HIP 1 1
0021 UX14269 P122521 ACCT 1 1
0022 UX14274 P122647 JOBFRZ 1 1
0023 UX14275 P122659 JOBFRZ 4 1
0024 UX14277 P775078 INTR 1 1
0025 UX14279 P122681 ELOG 1 1
0026 UX14281 P774974 TIMER 1 1
0027 UX14282 P774845 PXOPR 1 1
0028 UX14283 P775115 DUMP 1 1
0029 UX14288 P122764 SAF 1 1
0030 UX14289 P122767 CONFIG 1 1
0031 UX14290 P122776 HIPPI 1 1
0032 UX14291 P117933 CRON 1 1
0033 UX14294 P122781 PXPMS 4 1
0034 UX14296 P775177 VFL 1 1
0035 UX14297 P773384 NFS 1 1
0036 UX14297 P122639 NFS 1 1
0037 UX14299 P122772 NIS 5 1
0038 UX14302 P122639 NFS 1 1
0039 UX14305 P775158 ATM 1 1
0040 UX14306 P122933 DISKSETUP 1 1
0041 UX14308 P122447 WSIO 1 1
0042 UX14309 P122890 NFS 1 1
0043 UX14310 P122831 BASECMD 1 1
0044 UX14311 P122558 PXOPR 1 1
0045 UX14312 P122680 INIT 1 1
1 PROGRAM TEMPORARY FIX REPORT PAGE 0002
(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-------------
0046 UX14314 P775007 LP 1 1
0047 UX14315 P122564 NFS 1 1
0048 UX14316 P122564 NFS 1 1
0049 UX14317 P122797 TCPIP 1 1
0050 UX14321 P123054 HDU 1 1
0051 UX14322 P775243 IOS 1 1
0052 UX14326 P775254 TCPIP 1 1
0053 UX14328 P775258 NFS 1 1
0054 UX14339 P775007 LP 1 1
0055 UX14349 P123346 HDU 1 1
0056 UX14350 P123348 HDU 1 1
0057 UX14350 P123347 HDU 1 1
0058 UX14370 P123414 MAIL 1 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-UX12969 -P112145-IOS --PROGRAM FIX-----------IN -
1. A CHANNEL IS NOT RESET ALTHOUGH COPROCESSOR 4 INTERRUPT IS
GENERATED.
2. A MACHINE CHECK IS HANDLED INCORRECTLY.
-0002-UX13248 -P123273-ELOG --PROGRAM FIX-----------IN -
1. THE ERROR DAEMON OF IMPE MAY NOT BE STARTED.
2. THE ERROR DAEMON START PROCESSING CONTAINS AN ERROR.
-0003-UX13846 -P775008-LP --PROGRAM FIX-----------CALPR -
1. PRINTING FAILS UNDER THE FOLLOWING CONDITIONS:
1) A PRINTING REQUEST IS ISSUED TO CANON NETWORK PRINTER
LBP-730PS, AND
2) THE LPQ COMMAND IS EXECUTED.
2. PROCESSING TO DETERMINE THE QUEUING INFORMATION RETURNED FROM THE
CANON NETWORK PRINTER CONTAINS AN ERROR.
4. NONE
-0004-UX14123 -P774443-PXJOBSWAP --PROGRAM FIX-----------IN -
1. THE SWAPPING-OUT OF A JOB MAY FAIL UNDER THE FOLLOWING CONDITIONS:
1) A VFL FILE SYSTEM IS BEING USED AS A JOB SWAP AREA, AND
2) ANOTHER JOB IS ALREADY SWAPPED OUT IN THE ABOVE JOB SWAP AREA
TO WHICH THE JOB IS TO BE SWAPPED OUT.
2. THE JOB SWAP-OUT FUNCTION IS INCORRECT.
-0005-UX14183 -P775010-HIP --PROGRAM FIX-----------IN -
1. NO VALUE IS SET IN THE TRAFFIC INFORMATION OF THE CROSSBAR NETWORK
UNDER THE FOLLOWING CONDITION:
1) THE TRAFFIC INFORMATION OF THE CROSSBAR NETWORK IS COLLECTED BY
USING SNMP.
2. STATISTICAL INFORMATION OF THE INTER-PE COMMUNICATION DRIVER IS
NOT COLLECTED CORRECTLY.
-0006-UX14210 -P775079-CRON --PROGRAM FIX-----------CA -
1. AN AT COMMAND CANNOT SET A COMMAND EXECUTION DAY CORRECTLY (AN
ERROR OCCURS IF MARCH 1 IS SET AND A DAY OTHER THAN MARCH 1 IS
CHANGED TO THE DAY BEFORE IT) UNDER THE FOLLOWING CONDITIONS:
1) AN EXECUTION DAY IS SPECIFIED RELATIVELY (E.G. "NOW + 3 DAYS"
OR "12:00 FRI"), AND
2) THE STANDARD DATE OF RELATIVE DATES IS BEFORE MARCH 1 IN AN
YEAR THAT IS NOT A LEAP YEAR, AND
3) THE COMMAND EXECUTION DAY IS MARCH 1 OR LATER.
2. FEBRUARY IN A YEAR THAT IS NOT A LEAP YEAR IS ASSUMED TO CONTAIN
29 DAYS.
4. NONE
-0007-UX14216 -P121620-MAIL --PROGRAM FIX-----------IN -
1. AN INVALID CHARACTER IS INSERTED IN "USER-NAME@HOST-NAME" OF THE
RECEIVED: LINE UNDER THE FOLLOWING CONDITIONS:
1) A MAIL IS SENT, AND
2) THE IDENTD DAEMON IS OPERATING IN THE MAIL DESTINATION SYSTEM,
1 PROGRAM TEMPORARY FIX LIST PAGE 0002
DESCRIPTION OF : 1.SYMPTOM 2.CAUSE 3.ACTION TAKEN 4.APPLICABLE CONDITIONS
NO. PTF NO. SDR NO. COMPONENT FIX CLASSIFICATION SYMPTOM CODE
AND
3) THE IDENTD DAEMON RETURNS A USER NAME OF AN INVALID
CHARACTER STRING.
THIS ERROR HAS BEEN REPORTED IN CERT CA-95-05.
THE IDENTD DAEMON RECEIVES FROM THE SENDMAIL DAEMON THE
INFORMATION OF THE SENDER, CHECKS THE INFORMATION OF THE
SENDER, AND RETURNS TO THE SENDMAIL DAEMON CORRECT INFORMATION.
THE IDENTD DAEMON IS NOT SUPPORTED BY UXP.
2. WHEN THE SENDMAIL COMMAND IS USED IN MAIL TRANSMISSION, IT DOES
NOT CHECK THE CHARACTER STRING RECEIVED FROM THE IDENTD DAEMON OF
THE MAIL DESTINATION SYSTEM, AND USED IT IN THE RECEIVED: LINE AS
A USER NAME.
4. NONE
-0008-UX14218 -P121624-MAIL --PROGRAM FIX-----------IN -
1. IF THE FOLLOWING CONDITIONS ARE SET, A LOCAL USER CAN OBTAIN THE
EXECUTION AUTHORITY OF A OTHER USER BY USING THE .FORWARD FILE OF
THE OTHER USER:
1) THE OTHER USER BELONGING TO THE SAME GROUP HAS THE .FORWARD
FILE, AND
2) THE GROUP OF THE .FORWARD FILE HAS THE WRITE AUTHORITY, AND
3) A PROGRAM IS WRITTEN IN THE .FORWARD FILE, AND
4) A MAIL IS SENT TO THE USER.
THIS ERROR IS REPORTED IN CERT CA-96-25.
2. WHEN THE SENDMAIL COMMAND DELIVERS A MAIL, THE PERMISSION OF THE
.FORWARD FILE IS NOT CORRECTLY CHECKED.
4. NONE
-0009-UX14220 -P122000-MAIL --PROGRAM FIX-----------IN -
1. IN THE SENDMAIL COMMAND, IF A CHARACTER STRING INCLUDING A LINE
FEED CHARACTER IS SPECIFIED IN EITHER THE -F OPTION OR THE
ENVIRONMENT VARIABLE NAME, THE CHARACTERS FOLLOWING THE LINE FEED
CHARACTERS MAY BE USED FOR THE MAIL HEADER.
THIS ERROR IS REPORTED IN CERT CA-95-08.
2. THE SENDMAIL COMMAND DOES NOT CHECK WHETHER A LINE FEED CHARACTER
IS IN THE CHARACTER STRING SPECIFIED BY THE -F OPTION OR THE
ENVIRONMENT VARIABLE NAME.
4. NONE
-0010-UX14222 -P122001-MAIL --PROGRAM FIX-----------IN -
1. THE SENDMAIL COMMAND MAY EXECUTE A PROGRAM SET IN THE .FORWARD
FILE OF THE MAIL DELIVERY ADDRESS BY THE AUTHORITY OF THE DEFAULT
USER UNDER THE FOLLOWING CONDITIONS:
1) THE HOME DIRECTORY OF THE MAIL ADDRESS USER HAS THE .FORWARD
FILE WHERE PROGRAM EXECUTION IS SPECIFIED, AND
2) A MAIL IS SENT TO THE ADDRESS.
THIS ERROR IS REPORTED IN CERT CA-96-20.
2. THE SENDMAIL COMMAND DOES NOT CHECK SUFFICIENTLY THE AUTHORITY OF
THE EXECUTING USER THE PROGRAM SPECIFIED IN THE .FORWARD FILE.
4. NONE
1 PROGRAM TEMPORARY FIX LIST PAGE 0003
DESCRIPTION OF : 1.SYMPTOM 2.CAUSE 3.ACTION TAKEN 4.APPLICABLE CONDITIONS
NO. PTF NO. SDR NO. COMPONENT FIX CLASSIFICATION SYMPTOM CODE
-0011-UX14244 -P775028-FDDI --PROGRAM FIX-----------IN -
1. PERFORMANCE OF COMMUNICATIONS USING SBUS-FDDI MAY DETERIORATE DUE
TO THE OCCURRENCES OF LOST DATA.
2. THE SFC DRIVER RECEIVES DATA INCORRECTLY.
4. NONE
-0012-UX14245 -P122454-FDDI --OTHERS----------------FX -
1. AN INTERNAL INTERFACE WILL BE ADDED FOR THE SFC DRIVER.
3. APPLICATION MODIFICATION
-0013-UX14246 -P122502-JOBFRZ --PROGRAM FIX-----------CA -
1. JFADM, JFARENA, AND JFCONF DO NOT RUN IN A JOB WITH THE FROZEN
ATTRIBUTE.
2. THE JOB FREEZE COMMANDS ARE INCORRECT.
-0014-UX14251 -P774997-USRENV --PROGRAM FIX-----------IN -
1. THE AUDIT PROGRAM BECOMES INEFFECTIVE IF THE PASSWORD IS CHANGED
UNDER THE FOLLOWING CONDITIONS:
1) THE SYSTEM IS OPERATING MORE THAN ONE IPL, AND
2) THE LOCAL USER'S PASSWORD IS CHANGED BY USING THE PASSWD
COMMAND (THE PASSWORD IS CHANGED SUCCESSFULLY).
2. BECAUSE THE PROCESSING TO COPY /ETC/PASSWD OF P-PE OF THE PASSWD
COMMAND ONTO IMPE CONTAINS AN ERROR, LATER AUDIT PROCESSING FAILS.
4. NONE
-0015-UX14256 -P775134-IOS --PROGRAM FIX-----------IN -
1. A VARY COMMAND WITH A TARGET ID SPECIFIED FAILS IF IT IS
EXECUTED FOR A NONSCSI DEVICE.
2. A VARY COMMAND WITH A TARGET ID SPECIFIED IS PROCESSED INCORRECTLY
FOR A NONSCSI DEVICE.
-0016-UX14261 -P122417-NFS --PROGRAM FIX-----------CAMOUNT -
1. THE VALUE SPECIFIED IN THE RETRANS OPTION OF THE MOUNT(1M) DOES
NOT BECOME VALID.
2. ANALYSIS OF THE RETRANS OPTION CONTAINS AN ERROR.
-0017-UX14262 -P122503-NFS --PROGRAM FIX-----------MAMOUNT -
1. THE MOUNT(1M) OUTPUTS AN INAPPROPRIATE WARNING MESSAGE UNDER THE
FOLLOWING CONDITIONS, BUT THE MOUNTING COMPLETES NORMALLY:
- THE ACDIRMIN OPTION AND THE ACTIMEO OPTION ARE SPECIFIED AT THE
SAME TIME, AND
- THE ACDIRMIN OPTION IS SPECIFIED FIRST, AND
- A VALUE OTHER THAN 0 IS SPECIFIED IN THE ACDIRMIN OPTION.
2. WARNING MESSAGE OUTPUT PROCESSING WHEN AN EXCLUSIVE OPTION IS
SPECIFIED CONTAINS AN ERROR.
-0018-UX14265 -P774904-FORKEXEC --PROGRAM FIX-----------IN -
1. IPCS(1) OUTPUTS AN INVALID VALUE TO THE NATTCH COLUMN (THE NUMBER
OF PROCESSES BEING ATTACHED TO THE SHARED MEMORY) UNDER THE
FOLLOWING CONDITIONS:
1) THE PROCESS WHERE THE SHARED MEMORY IS BEING ATTACHED GENERATES
1 PROGRAM TEMPORARY FIX LIST PAGE 0004
DESCRIPTION OF : 1.SYMPTOM 2.CAUSE 3.ACTION TAKEN 4.APPLICABLE CONDITIONS
NO. PTF NO. SDR NO. COMPONENT FIX CLASSIFICATION SYMPTOM CODE
A CHILD PROCESS BY EXECUTING VFORK(2), AND
2) THE GENERATED CHILD PROCESS EXECUTES EXEC(2).
2. PROCESSING RELATED TO SHARED MEMORY OF VFORK(2) CONTAINS AN ERROR.
-0019-UX14267 -P122629-FS --PROGRAM FIX-----------AB -
1. A SYSTEM PANIC MAY OCCUR UNDER THE FOLLOWING CONDITIONS:
1) A FILE IS TRANSFERRED TO THE VFL FILE SYSTEM, AND
2) THE FILE TRANSFER IS MADE USING FTP, AND
3) THE TRANSFER MODE IS THE BINARY MODE.
2. THE WRITE PROCESSING WHICH FTP USES CONTAINS AN ERROR.
-0020-UX14268 -P122634-HIP --PROGRAM FIX-----------PR -
1. PERFORMANCE MAY BE DEGRADED UNDER THE FOLLOWING CONDITIONS:
1) THE CROSSBAR NETWORK IS BUILT WITH THE POINT-TO-POINT
CONFIGURATION, AND
2) MULTIPLE PES ARE STARTED, AND THE INTER-PE COMMUNICATION
CONTROL DAEMON IS STARTED ON EACH PE.
2. PERFORMANCE OF THE NETWORK INTERFACE MONITORING OF THE INTER-PE
COMMUNICATION CONTROL DAEMON IS NOT CONSIDERED SUFFICIENTLY.
-0021-UX14269 -P122521-ACCT --PROGRAM FIX-----------IN -
1. ACCTWRT(2) OPERATES NORMALLY BUT THE RETURN VALUE MAY INDICATE AN
ERROR UNDER THE FOLLOWING CONDITION:
1) ACCTWRT(2) IS EXECUTED FROM EITHER S-PE OR SIOPE.
2. THE RETURN VALUE OF ACCTWRT(2) IS NOT INITIALIZED.
4. NONE
-0022-UX14274 -P122647-JOBFRZ --PROGRAM FIX-----------MA -
1. WHEN FREEZING OF A JOB FAILS, EVEN IF THE JOB IS CONTINUING,
MESSAGE "JOB WAS EXITED." IS OUTPUT IN THE REPORT MAIL.
2. JOB STATUS IS DETERMINED INCORRECTLY BY THE JOB FREEZE FUNCTION.
-0024-UX14277 -P775078-INTR --PROGRAM FIX-----------CA -
1. A PROCESS WHICH SHOULD TERMINATE ABNORMALLY AT RECEIVING A SIGNAL
DOES NOT TERMINATE ABNORMALLY, BUT HANGS UP UNDER EITHER THE
FOLLOWING CONDITIONS:
- AN ATTEMPT IS MADE TO ACCESS AN INVALID AREA IN THE RANGE FROM
0X80400000 TO 0XC0000000, OR
- AN ATTEMPT IS MADE TO READ AND EXECUTE AN INSTRUCTION FROM THE
AREA TO WHICH NO VIRTUAL AREA IS ALLOCATED.
2. THE INTERRUPT PROCESSING CONTAINS AN ERROR.
-0025-UX14279 -P122681-ELOG --PROGRAM FIX-----------IN -
1. ERRDEMON MAY TERMINATE ABNORMALLY WITH OUTPUTTING CORE WHEN
MRCE TERMINATES ABNORMALLY.
2. TERMINATION OF ERRDEMON CONTAINS AN ERROR.
-0026-UX14281 -P774974-TIMER --PROGRAM FIX-----------IN -
1. IF THE SECONDARY PE IS STARTED UNDER THE FOLLOWING CONDITIONS, THE
GLOBAL PATH OF THE PE MAY NOT BE MOUNTED:
- AFTER THE SYSTEM IS STARTED, SYSTEM TIME IS SET BY USING
1 PROGRAM TEMPORARY FIX LIST PAGE 0005
DESCRIPTION OF : 1.SYMPTOM 2.CAUSE 3.ACTION TAKEN 4.APPLICABLE CONDITIONS
NO. PTF NO. SDR NO. COMPONENT FIX CLASSIFICATION SYMPTOM CODE
STIME(2). THE FOLLOWING TWO STANDARD COMMANDS ISSUE STIME(2):
- DATE(1) (ONLY WHEN THE ABSOLUTE TIME IS SPECIFIED)
- RDATE(1M)
2. PROCESSING OF STIME(2) CONTAINS AN ERROR.
-0027-UX14282 -P774845-PXOPR --PROGRAM FIX-----------ABS -
1. CP(M) MAY FAIL UNDER THE FOLLOWING CONDITIONS:
1) A MULTI-PE SYSTEM IS USED, AND
2) A PE FAILURE OCCURS FREQUENTLY.
2. THE RESOURCE RELEASE PROCESSING WHEN A PE FAILURE OCCURS CONTAINS
AN ERROR.
-0028-UX14283 -P775115-DUMP --PROGRAM FIX-----------IN -
1. STAND-ALONE DUMP INFORMATION COLLECTION ON A DISK MAY FAIL IN A
SYSTEM WITH RAID (F6401H) AND ALLEGRO.
2. STAND-ALONE DUMP INFORMATION IS COLLECTED INCORRECTLY ON A DISK.
-0029-UX14288 -P122764-SAF --PROGRAM FIX-----------AB -
1. A NETWORK ADAPTER MAY BECOME UNUSABLE UNDER THE FOLLOWING
CONDITIONS:
1) A HARDWARE ERROR OCCURS IN A NETWORK ADAPTER (HIPPI, FDDI, ATM,
ETHERNET), AND
2) A SYSTEM IS UNDER A HEAVY LOAD.
2. ERROR MONITORING DAEMON PHERRD RECEIVES EVENTS INCORRECTLY.
-0030-UX14289 -P122767-CONFIG --PROGRAM FIX-----------CACMP_UNIX -
1. /STAND/UNIX OF IMPE MAY NOT BE UPDATED.
2. PROCESSING TO UPDATE /STAND/UNIX OF IMPE CONTAINS AN ERROR.
-0031-UX14290 -P122776-HIPPI --PROGRAM FIX-----------AB -
1. THE SYSTEM MAY FAIL UNDER THE FOLLOWING CONDITION:
- AN ERROR OF THE SBUS CHANNEL OCCURS DURING ACCESS TO THE HIPPI
ADAPTOR.
2. PROCESSING OF THE HIPPIMD DRIVER WHEN A COMPLETION REPORT OF
INVALID CONTENTS IS RECEIVED FROM THE HIPPI ADAPTOR CONTAINS AN
ERROR.
4. NONE
-0032-UX14291 -P117933-CRON --PROGRAM FIX-----------CA -
1. AN AT COMMAND TERMINATES ABNORMALLY UNDER THE FOLLOWING
CONDITIONS:
1) ENVIRONMENT VARIABLE DATEMSK IS NOT SET, AND
2) A RELATIVE DATE IS SPECIFIED, AND
3) THE STANDARD DAY IS THE AT COMMAND EXECUTION DAY, AND
4) THE AT COMMAND EXECUTION DAY IS IN 2000 OR LATER.
2. 2000 AND LATER ARE NOT CONSIDERED WITH THE AT COMMAND IN YEAR
ANALYSIS.
4. NONE
-0034-UX14296 -P775177-VFL --PROGRAM FIX-----------IN -
1. A PROCESS TO ACCESS THE MOUNT POINT DIRECTORY OF VFL-FS FAILS
1 PROGRAM TEMPORARY FIX LIST PAGE 0006
DESCRIPTION OF : 1.SYMPTOM 2.CAUSE 3.ACTION TAKEN 4.APPLICABLE CONDITIONS
NO. PTF NO. SDR NO. COMPONENT FIX CLASSIFICATION SYMPTOM CODE
UNDER THE FOLLOWING CONDITIONS:
1) RETRIEVAL PROCESSING FOR A ".." FILE IS ISSUED TO THE MOUNT
POINT DIRECTORY, AND
VFL-FS DOES NOT SUPPORT THE ROOT FILE SYSTEM; THE SYMPTOM
CURRENTLY OCCURS UNDER NO CONDITIONS BUT THE FOLLOWING:
2) THE RESOURCE UNDER THE MOUNT POINT DIRECTORY OF VFL-FS IS
MOUNTED, AND
3) MFS-V3 MOUNTS THE RESOURCE, AND
4) THE RESOURCE IS ACCESSED FROM THE CLIENT.
2. FILES UNDER THE MOUNT POINT DIRECTORY OF VFL-FS ARE RETRIEVED
INCORRECTLY.
-0035-UX14297 -P773384-NFS --PROGRAM FIX-----------PR -
1. SYSTEM RESPONSE IS DETERIORATED UNDER THE FOLLOWING CONDITIONS:
1) A LARGE FILE IS PRESENT IN A UFS OR S5 FILE SYSTEM, AND
2) THE LARGE FILE IS ACCESSED REPEATEDLY FROM A CLIENT VIA NFS FOR
A LONG TIME, AND
3) THE PATH NAME INFORMATION ABOUT THE LARGE FILE IS DISCARDED
FROM A DIRECTORY NAME CACHE.
2. A FILE IS ACCESSED VIA NFS INCORRECTLY.
-0036-UX14297 -P122639-NFS --PROGRAM FIX-----------IN -
1. EVEN IF THE FILE IS DELETED, RELEASE THE DATA BLOCK IN THE FILE
SYSTEM MAY BE DELAYED UNDER THE FOLLOWING CONDITIONS:
1) THE FILE SYSTEM WHICH IS NOT UFS/SFS IS USED, AND
2) THE HOST WHICH HAS THE FILE SYSTEM OF ITEM 1) IS TO BE THE
NFS SERVER AND THEN NFS MOUNT IS MADE ON THE FILE SYSTEM OF
ITEM 1), AND
3) READ/WRITE IS EXECUTED FROM THE NFS CLIENT'S SIDE FOR THE
FILES ON FILE SYSTEM MOUNTED ON ITEM 2), AND
4) FILE WHICH IS MADE READ/WRITE ON ITEM 3) IS DELETED.
2. THE METHOD OF OPERATING THE DIRECTORY NAME CACHE OF THE
NFS SERVER WAS INCORRECT.
-0037-UX14299 -P122772-NIS --OTHERS----------------CA -
1. ALTHOUGH NIS MAP TRANSFER IS COMPLETED, THE YPPUSH COMMAND OUTPUTS
THE ERROR MESSAGE "NO RESPONSE FROM YPXFR ON HOST-NAME" AND MORE
THAN 10 MINUTES ELAPSES BEFORE THE END OF THE COMMAND UNDER THE
FOLLOWING CONDITIONS:
1) UXP/V IS OPERATING AS THE NIS SLAVE SERVER, AND
2) THE YPPUSH COMMAND IS EXECUTED FROM SOLARIS 2.X (WHERE THE NIS
NAME SERVICE TRANSITION KIT HAS ALREADY BEEN APPLIED) TO UXP/V.
DEVELOPED SYMPTOM:
1) IF YPMAKE(CD /VAR/YP;MAKE) IS EXECUTED ON THE NIS MASTER SERVER
(SOLARIS 2.X), IT TAKES SOME TIME TO ACCOMPLISH THE ASSIGNMENT.
2. TO THE NIS SLAVE SERVER, SOLARIS 2.X YPPUSH SENDS AN INCORRECT
PORT NUMBER FOR ITS OWN.
3. THE WAY IN WHICH YPXFR GENERATES THE CLIENT HANDLER FOR
COMMUNICATIONS WITH YPPUSH WILL BE CORRECTED.
-0038-UX14302 -P122639-NFS --PROGRAM FIX-----------IN -
1 PROGRAM TEMPORARY FIX LIST PAGE 0007
DESCRIPTION OF : 1.SYMPTOM 2.CAUSE 3.ACTION TAKEN 4.APPLICABLE CONDITIONS
NO. PTF NO. SDR NO. COMPONENT FIX CLASSIFICATION SYMPTOM CODE
1. EVEN IF THE FILE IS DELETED, RELEASE THE DATA BLOCK IN THE FILE
SYSTEM MAY BE DELAYED UNDER THE FOLLOWING CONDITIONS:
1) THE FILE SYSTEM WHICH IS NOT UFS/SFS IS USED, AND
2) THE HOST WHICH HAS THE FILE SYSTEM OF ITEM 1) IS TO BE THE
NFS SERVER AND THEN NFS MOUNT IS MADE ON THE FILE SYSTEM OF
ITEM 1), AND
3) READ/WRITE IS EXECUTED FROM THE NFS CLIENT'S SIDE FOR THE
FILES ON FILE SYSTEM MOUNTED ON ITEM 2), AND
4) FILE WHICH IS MADE READ/WRITE ON ITEM 3) IS DELETED.
2. THE METHOD OF OPERATING THE DIRECTORY NAME CACHE OF THE
NFS SERVER WAS INCORRECT.
-0039-UX14305 -P775158-ATM --PROGRAM FIX-----------AB -
1. AN ATMCAPSTAT(1M) MAY TERMINATE ABNORMALLY AND A SYSTEM MAY PANIC
UNDER THE FOLLOWING CONDITION:
- SEVEN OR MORE ATM VIRTUAL CHANNELS (VCS) ARE DEFINED IN
COMMUNICATION USING ATM.
2. THE STATISTICAL INFORMATION COLLECTION INTERFACE BETWEEN THE
ATMCAPSTAT(1M) AND ATM DRIVER CONTAINS AN ERROR.
-0040-UX14306 -P122933-DISKSETUP --PROGRAM FIX-----------DC -
1. THE TIME REQUIRED FOR PHYSICAL FORMATTING OF F8927C (M2949) IS NOT
WRITTEN IN THE REFERENCE MANUAL FOR DISKFORMAT(1M).
2. WHEN F8927C IS SUPPORTED, A DESCRIPTION OF THE TIME REQUIRED FOR
PHYSICAL FORMATTING OF F8927C (M2949) IS NOT ADDED TO THE
REFERENCE MANUAL FOR DISKFORMAT(1M).
-0041-UX14308 -P122447-WSIO --PROGRAM FIX-----------WS -
1. THE WSIO ADAPTER IS INAPPROPRIATELY TAKEN OFFLINE UNDER THE
FOLLOWING CONDITIONS:
1) A MISSING INTERRUPT OCCURS AT AN SCSI DEVICE, AND
2) THE WSIO DRIVER TERMINATES THE ISSUED I-O FUNCTION FORCIBLY,
USING HDCR, AND
3) THE ISSUED I-O FUNCTION REPORTS AN SCSI BUS HANG.
2. A PROCESSING WHEN OCCURRING A MISSING INTERRUPT PROCESSING OF THE
WSIO DRIVER IS NOT BEING CONSIDERED.
-0042-UX14309 -P122890-NFS --PROGRAM FIX-----------MA -
1. INTERVAL BETWEEN NFS FILE ACCESS AND TIME-OUT MESSAGE DISPLAY
DIFFERS FROM THE EXPLANATION IN A MANUAL UNDER THE FOLLOWING
CONDITIONS:
1) NFSV2 MOUNTING IS DONE, AND
2) MOUNT SUBOPTION "HARD,INTR" IS SPECIFIED, AND
3) MOUNT SUBOPTION "RETRANS" IS NOT SPECIFIED OR A LEVEL NOT LOWER
THAN 5 IS SPECIFIED.
4) NO RESPONSE IS RECEIVED FROM A SERVER OR A TOO LONG TIME
ELAPSES BEFORE A RESPONSE FROM A SERVER IS RECEIVED.
2. WHETHER A MESSAGE IS TO BE DISPLAYED IS JUDGED BEFORE RETRY OF A
REQUEST WITH WHICH TIME-OUT OCCURS. AN INCORRECT CONDITION IS USED
IN THIS JUDGMENT.
4. NONE
1 PROGRAM TEMPORARY FIX LIST PAGE 0008
DESCRIPTION OF : 1.SYMPTOM 2.CAUSE 3.ACTION TAKEN 4.APPLICABLE CONDITIONS
NO. PTF NO. SDR NO. COMPONENT FIX CLASSIFICATION SYMPTOM CODE
-0043-UX14310 -P122831-BASECMD --PROGRAM FIX-----------DC -
1. ONLINE MANUALS CONTAIN ERRORS.
2. THE DATE(1), CTIME(3C), AND GETDATE(3C) MANUALS CONTAIN ERRORS
(MISPRINT/OMITTED WORD).
-0044-UX14311 -P122558-PXOPR --PROGRAM FIX-----------MA -
1. THE FOLLOWING MESSAGE IS DISPLAYED ON A CONSOLE IN IMPE
REACTIVATION:
OPR:9999:NFS_SV_UP(K)DON'T CALL
2. WHETHER THE MESSAGE IS TO BE DISPLAYED IS JUDGED INCORRECTLY.
-0045-UX14312 -P122680-INIT --PROGRAM FIX-----------DC -
1. ENTERING A PASSWORD IN SINGLE USER MODE FAILS UNDER THE FOLLOWING
CONDITION:
1) /ETC/INITTAB HAS BEEN DELETED.
2. THE REFERENCE MANUAL ON INIT(1M) IS INCORRECT.
-0046-UX14314 -P775007-LP --PROGRAM FIX-----------CALP -
1. THE SAME DOCUMENT MAY BE PRINTED REPEATEDLY UNDER THE FOLLOWING
CONDITIONS:
1) THE REMOTE PRINTER IS THE BSD TYPE REMOTE SERVER, AND
2) THE TIME-OUT TIME IS SET TO "0" IN THE LPSYSTEM COMMAND (THE T
OPTION).
2. THE TIME-OUT TIME SETTING METHOD IS NOT EXPLAINED SUFFICIENTLY IN
THE ONLINE MANUAL LPSYSTEM(1M).
4. NONE
-0047-UX14315 -P122564-NFS --PROGRAM FIX-----------CAMOUNT -
1. A VALUE EQUAL TO OR LARGER THAN 65536 IS SPECIFIABLE IN THE PORT
OPTION OF MOUNT(1M) (SUCH VALUE IS NOT SPECIFIABLE IN AUTOMOUNT).
2. THE SPECIFIABLE VALUE RANGE IS NOT CHECKED.
-0048-UX14316 -P122564-NFS --PROGRAM FIX-----------CAMOUNT -
1. A VALUE EQUAL TO OR LARGER THAN 65536 IS SPECIFIABLE IN THE PORT
OPTION OF MOUNT(1M) (SUCH VALUE IS NOT SPECIFIABLE IN AUTOMOUNT).
2. THE SPECIFIABLE VALUE RANGE IS NOT CHECKED.
-0049-UX14317 -P122797-TCPIP --PROGRAM FIX-----------WS -
1. THE SYSTEM MAY FALL INTO A PANIC AT WATCHDOGTIMEOUT (WDT) UNDER
THE FOLLOWING CONDITIONS:
1) 1024 OR A GREATER VALUE IS SPECIFIED BOTH IN THE READ-WRITE
LENGTH FIELD AND THE TCP WINDOW SIZE FIELD IN FILE
/ETC/INET/TISPPARAM, AND
2) LOOPBACK COMMUNICATIONS IS CARRIED ON WITH FTP.
2. TCP MANAGES THE SEND BUFFER INCORRECTLY.
-0050-UX14321 -P123054-HDU --PROGRAM FIX-----------IN -
1. THE LAST TWO BYTES OF THE FLAG CODE OF HIPPI IS ALWAYS "0000".
2. AN INVALID VALUE IS SET AS THE OFFSET LOCATION FOR REFERENCING THE
ERROR CODE.
1 PROGRAM TEMPORARY FIX LIST PAGE 0009
DESCRIPTION OF : 1.SYMPTOM 2.CAUSE 3.ACTION TAKEN 4.APPLICABLE CONDITIONS
NO. PTF NO. SDR NO. COMPONENT FIX CLASSIFICATION SYMPTOM CODE
-0051-UX14322 -P775243-IOS --PROGRAM FIX-----------WS -
1. IF LOAD IS APPLIED ON THE SBUS CHANNEL ADAPTERS (HIPPI, ATM,
FDDI), THE SYSTEM MAY STOP WHEN A TIME-OUT IS DETECTED BY THE
WATCH DOG TIMER.
2. INTERRUPT PROCESSING OF IOS CONTAINS AN ERROR.
-0052-UX14326 -P775254-TCPIP --PROGRAM FIX-----------IN -
1. TCP CONNECTION ESTABLISHMENT MAY TAKE FIVE SECONDS OR MORE UNDER
THE FOLLOWING CONDITIONS:
(1) TCP IS USED.
(2) A NEW CONNECTION REQUEST IS ISSUED WITH THE SAME COMMUNICATION
PAIR AS TCP CONNECTION IN TIME_WAIT STATUS.
2. TCP CONNECTION ESTABLISHMENT CONTAINS AN ERROR.
-0053-UX14328 -P775258-NFS --PROGRAM FIX-----------ABSXXX -
1. A SYSTEM PANICS UNDER THE FOLLOWING CONDITIONS:
- A REMOTE RESOURCE IS MOUNTED IN NFS VERSION 3, AND
- FILES UNDER A DIRECTORY ARE REFERENCED AS OPERATION FOR THE
REMOTE RESOURCE, AND
- ACQUISITION OF INFORMATION ABOUT FILES UNDER THE DIRECTORY FAILS
IN AN NFS SERVER.
2. RESPONSE DATA FROM AN NFS SERVER IS DECODED INCORRECTLY.
-0054-UX14339 -P775007-LP --PROGRAM FIX-----------CALP -
1. THE SAME DOCUMENT MAY BE PRINTED REPEATEDLY UNDER THE FOLLOWING
CONDITIONS:
1) THE REMOTE PRINTER IS THE BSD TYPE REMOTE SERVER, AND
2) THE TIME-OUT TIME IS SET TO "0" IN THE LPSYSTEM COMMAND (THE T
OPTION).
2. THE TIME-OUT TIME SETTING METHOD IS NOT EXPLAINED SUFFICIENTLY IN
THE ONLINE MANUAL LPSYSTEM(1M).
4. NONE
-0055-UX14349 -P123346-HDU --PROGRAM FIX-----------IN -
1. CAUSE OF AN ERROR MAY NOT BE DISTINGUISHED BY THE FLAG CODE OF
HIPPI OBR.
2. INFORMATION WHICH IS SET IN THE CURRENT FLAG CODE IS NOT SET
WITH ASSUMING THE CASE OF STATUS CODE NOT BEING SET IN ERROR LOG,
BUT IS SET WITH THE STATUS CODE FIXED.
-0056-UX14350 -P123348-HDU --PROGRAM FIX-----------IN -
1. A FLAG CODE IS NOT REPORTED FOR AN ERROR OCCURRING AFTER AN INTVL
TIME ELAPSES.
2. FLAG CODE INFORMATION FOR WHICH INTVL TIME ELAPSES IS NOT DELETED
WHEN THE SAME FLAG CODE IS CREATED.
-0057-UX14350 -P123347-HDU --PROGRAM FIX-----------IN -
1. NOT ALL FLAG CODES ARE REPORTED IF ERROR LOG INFORMATION IS
COLLECTED CONTINUOUSLY.
2. THE FLAG CODE STORING BUFFER BUSY FLAG IS SET INCORRECTLY.
1 PROGRAM TEMPORARY FIX LIST PAGE 0010
DESCRIPTION OF : 1.SYMPTOM 2.CAUSE 3.ACTION TAKEN 4.APPLICABLE CONDITIONS
NO. PTF NO. SDR NO. COMPONENT FIX CLASSIFICATION SYMPTOM CODE
-0058-UX14370 -P123414-MAIL --PROGRAM FIX-----------IN -
1. A MAIL TO THE ALIAS OF THE FOLLOWING CONDITIONS IS RETURNED AS AN
ERROR MAIL:
1) AN ALIAS DEFINITION OF THE /USR/LIB/ALIASES FILE IS FOUND, AND
2) THE ":INCLUDE: FILE" SPECIFICATION IS FOUND, AND
3) A COMMAND IS SPECIFIED IN THE FILE.
THE FOLLOWING IS THE ERROR MESSAGE FOR THE ERROR MAIL:
550 FILES: LINE LINE-NUMBER: COMMAND ... ADDRESS :INCLUDE: FILE IS
UNSAFE FOR MAILING TO PROGRAMS
2. NOTES ON THE ":INCLUDE: FILE" SPECIFICATION OF THE ALIASES FILE
ARE MISSING FROM THE ONLINE MANUAL OF ALIASES(4).
4. NONE
** END **