1. Attempt to delete JECL continuation statement in SLI-member (by using sequence number) results garbage on the screen (1R33D message), or 1Q2CI Segment translation exception and POWER ABEND followed by dump creation.
2. Specification of 'RBM=n' operand in the '* $$ PUN' statement can result 1QZ0I (RC=0045) error message which follows dump creation.

1. When displaying the CRE queue, duplicate entries may be shown.
2. PDISPLAY Q takes to much time to show extended queue information.
3. PDISPLAYqueue,TAPE=cuu,OUT=CON shows header line for each entry.

* DO NOT INSTALL (PE) *
Please install DY46608.

1. When VSE/POWER's own 'TI00' Timer Exit routine is disabled by a user exit coded 'SETIME r1,r2' with ECB, or by replacement with OEM own Timer Exit routine, then the Time Event scheduling functions will come to a halt.
2. VSE/POWER Networking entries that are transmitted via RSCS or AIX nodes will produce a "transmission acceptance" message even though the entries did not specify the NTFY= operand.
3. A compile error occurred for the module IPW$$MM due to an error in the message 1QE7I.

* DO NOT INSTALL (PE) *
Please install DY46608.

1. For PALTER LST,H,USER=Rnnn with more than 500 entries in disp. or non disp. chain, command processor loops on writing to queue file - while DMB is unlocked periodically (fortunately).
2. If data is included via * $$ SLI and * $$ DATA statements and a /*$SLI statement is used to end data to be included, results are unpredictable.
3. If in a * $$ LST/PUN statement the PRI= operand is specified without a value, the priority value for the created queue entries shows up as a blank or ','.
4. Trace message 1RT2I ends sometimes with (ACT)NT) wherey the 'NT)' are meaningless.

1. When during profile processing of dyn. part. 'Xn' the partition is cancelled by operator, then 1Q6FA RC=0002 is issued and class 'X' is disabled for job selection.
2. For CRE-queue browsing and Restart to Active the q-rec field QRC2 is used at length of 16 bytes, but cleared in implicite QRC2 length of 32 bytes.

1. When data is received from JES2 (or RSCS) via a SNA link, ending blanks may be lost.
2. When BTRNC=NO has been specified in the PSTART PNET,node command and the hardcopy file wraps around, no information is available whether it has been specified or not.
3. Operating systems other than z/VSE do not support multihoming (as done by z/VSE offering the IPEXTRAD parameter in the PNODE macro) for TCP links. Connections can not be established, message 1RT5I is issued.

1. Palter command has to commit the changes to q-file on disk. When bulk alteration is requested, this may take seconds while DMB is locked - disallowing tasks to gain control that need the DMB resource.
2. The Dsect MAPPOWJB for GETFLD FIELD=POWJOB provides Jobname and Jobnumber of the active VSE/POWER job, but the Jobclass is missing.
3. When m/d/y pattern has been changed during VSE/POWER warm start (e.g. during FSU), CRDATE= specifications are interpreted in the current e.g. d/m/y pattern . Hence entries created before the warm start can not be manipulated by CRDATE= to isolate them.
4. The SORT=NEW/OLD display presents display lines in standard format. The sort criteria 'creation date + time' are hidden in the 2nd/3rd line of a FULL=YES display (see D=... and T=....).

When FSU from VSE/ESA 2.7.0 or 2.7.1 or 2.7.2 is started and one VSE/POWER data file extent does not start on Cylinder Boundary (Data file on CKD), the warm start of the VSE/POWER queues fails on z/VSE 3.1 with msg 1Q19I INVALID DATA FILE EXTENT, RC=0003 . VSE/POWER is terminated and FSU can not continue.

1. PNET usage:
   1. The JES copy count, for example COPIES=(164,(24,...,17)) of 164 in NDHGDSCT is destroyed when sending 3800 output through an intermediate VSE/POWER PNET node (replaced by number of copy groups).
   2. Job/output data originating from non VSE/POWER (e.g. JES, RSCS) nodes are transmitted with trailing blanks but these are removed forever when data is spooled by VSE/POWER as final or intermediate node.
   3. If job/output data originating from non VSE/POWER (e.g. JES, RSCS) nodes contain trailing blanks and are forwarded to another JES, RSCS, the record length is different from the original record length.
   4. If output data originating from non VSE/POWER (e.g. JES, RSCS) nodes consist of various parts with different record lengths and are forwarded to another JES, RSCS, the record lengths are different form the original record lengths.
2. The VM/CMS user of the VSECMD command does not receive a VSE/POWER response message for the PACCOUNT command.
3. PDISPLAY command:
   1. The PDISPLAY ..,LIMIT=NN value allows only a maximum of 99, especially for PDISPLAY BIGGEST. This is too little for big queues.
   2. The PDISPLAY RDR/LST/PUN/XMT cmd presents q-entries sorted by class but not by creation-date, i.e. not by 'age' of the entries.
4. VSE/POWER recovery startup may fail 1Q2CI CC=21, ILLEGAL SVC, PHASE=IPW$$NU, TASK='P PS', even more in VSE/POWER shared environment.

1. When PNET receiver task stalls due to 1Q38A NO DASD AVAILABLE, then the PDRAIN command is not effective, but receiver remains in wait-for-Data-File-DBLK.
2. When SAS-PUT-Job/Out task stalls due to 1Q38A NO DASD AVAILABLE, then the PSTOP SAS command is not effective, but SAS-PUT task remains in wait-for-Data-File-DBLK.

1. Unprintable characters in HDR1-part of message 1QB9A may abend VSE/POWER with message 1Q2CI with SEGM. TRANSL. EXCEPTION in phase IPW$$MX.
2. The error handling of PNET SSL for the GSKSSOCINIT call will ignore an I/O error (RC=-00000010 or the equate FRCN0010). Also an ERRNO=00001102 (EWOULDBLOCK) handling leads to an IDUMP in the cases of
   • GSKSSOCREAD
   • GSKSSOCWRITE
   • GSKSSOCCLOSE
   • GSKSSOCRESET
3. PACCOUNT PUN creates IDUMP indicated by msg 1Q2JI in IPW$$02 when data file is full and no DBLKGPs are available.

1. 1. When all DBLKGP cushion elements are used and FREE DBLK GROUP count is 0, the next request for a queue display via Spool Access Support, e.g. by IUI, fails with 1QZ0I RC=0025 in module IPW$$DQ.
2. 2. FULL queue display does not show creation time.

1. DUETIME operand does not support to calculate a runtime dependant on time when job entered system.
2. The record count of a list output received from a JES2/3 is different than the record count displayed by JES2/3.

1. Any other VSE/POWER subtask than Async. Service Subtask (-AS), namely DS/LS/SD/SN/S1/TD/TI should take IDUMP when being cancelled under all circumstances - Cancel Code '09' (LIOCS) should not make an exception.
2. When long running CICS/VTAM/TCP-IP jobs with DISP=D/K are replaced by new version, the old job in DISP=* cannot be PALTER'ed to DISP=D so that it vanishes at system shutdown and allows the new version to be released at system startup. Instead the old version is released once more then.

1. Destroyed VSE/POWER class anchors or chain pointers to the free-q-rec chain result in display of quasi empty 'free' queue records, which may be many.
2. When being used to 'number-of-spooled-pages' for LST queue entries and altering them to the XMT queue, then no more pages but LINES are presented, what may be confusing.
3. 1)When remote node sends FCS bytes not equal to X'8FCF', a loop of IDUMP macro-calls and message 1RTLI may occur. 2) When remote node sends incorrect BSC frames, the connection hangs and message 1RC1I is issued.