First group of WAVV 1995 IBM Requirements
First group of WAVV 1995 IBM Requirements
CATEGORY VSE
PRODNAME VSE/POWER
PRIORITY 1.2
CLASSIF L
TITLE Power elimination of AUTONAME job entry
DESCRIPT Allow power startup option to assure that no jobs that would
acquire the name AUTONAME are accepted and put on the rdr
queue.
BENEFIT Allow better policing of power queue, fewer cases of lost
output, wasted processing.
TLIMIT As possible - it's been like this forever, another year or so
can't hurt.
SOLUTION Startup option or generation option; either would work.
IMPACT Continued aggravation for users, operators, output control
personnel.
REFINFO This is WAVV User Group Requirement WGxxxx026
Voting: -3=1 -1=3 0=18 +1=18 +2=11 +3=3 no other votes
KEYWORDS AUTONAME POWER
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group
CUSTNAME Barry Stratton
CPHONE (415) 362-3310 x 721
CATEGORY VSE
SUBCAT VSE/AF
PRODNAME VSE/ESA
PRIORITY 2.0
CLASSIF L
TITLE Console Prompt after forced cancel
DESCRIPT Responding CANCEL to a console message (after a // PAUSE, or in
response to a message demanding a reply) causes job to begin to
cancel, but before cancellation is complete, console prompt
returns as if more information may be entered. No matter what
is entered, once EOB is pressed, partition cancellation
continues as if nothing has been entered.
BENEFIT This situation is a confusing nuisance - benefit is reduction
of confusion among operators, and removal of need to reply to a
nuisance message, the reply to which simply gets ignored.
TLIMIT NO TIME LIMIT PROVIDED BY REQUEST AUTHOR
SOLUTION Don't do that.
REFINFO This is WAVV USER GROUP Requirement WGxxxx025
Voting: -1=6 0=10 +1=29 +2=23 No other votes
KEYWORDS VSE, JOB CONTROL, CANCEL
INITBY CUST
CNTRYCD 600
COMPANY WAVV User GROUP
CUSTNAME Ben Moyle
CPHONE (612) 933-2885
SUBCAT VSE/AF
PRODNAME VSE/ESA
PRIORITY 2.1
CLASSIF L
TITLE VSE LIBDEF limitations
DESCRIPT Raise the limit of libraries that can be defined in a LIBDEF
from the current limit of 15 to as high as 255.
Update entered by Judith Jay 19960911 15:15:25
Raise the limit of libraries that can be defined in a LIBDEF
from the current limit of 15 to as high as 255.
BENEFIT Many products are best kept in their own libraries, and IBM
delivers VSE in such a way as to use more than a few for its
own purposes. 15 is simply not enough any more, paqrticularly
when faced with the need to install new subsets or test
versions of currently operational products.
TLIMIT Next release?
IMPACT The result of this condition (insufficient libdef slots) is
that we are forced to do much manipulation of libraries and
JCL, leading to unnecessary erors and recovery processes.
REFINFO This is WAVV User Group Requirement WGxxxx024
Voting: 0=4 +1=14 +2=42 +3=38 no other votes
KEYWORDS LIBDEF
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group
CUSTNAME Barry Stratton - Judith Jay
CPHONE (415) 362-3310 x 721
CATEGORY VSE
SUBCAT GENERAL
PRODNAME VSE/ESA ON P390
PRIORITY 2.2
CLASSIF L
TITLE Pcopy Program for VSE/ESA on P390
DESCRIPT There needs to be a batch program for VSE/ESA that provides the
same function that the PCOPY command provides for VM on the
PC Server 500 System 390.
BENEFIT This function would provide a very very fast method of moving
data from the VSE environment to the LAN environment.
TLIMIT NO TIME LIMIT PROVIDED BY AUTHOR
SOLUTION The solution should include a batch program as well as a
callable subroutine to provide the same functions.
REFINFO This is WAVV user Group Requirement WGxxxx023
Voting: +1=3 +2=26 +3=9 no other votes
KEYWORDS VM/ESA PCOPY facility for VSE/ESA on PC Server 500 S/390
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group
CUSTNAME Charles Rice - Judith Jay
CATEGORY VSE
SUBCAT VSE/AF
PRIORITY 1.7
CLASSIF S
TITLE SDUMP MACRO ENHANCEMENT - show register sets
DESCRIPT SDUMP should produce, in addition to all the data areas dumped,
the contents of all register sets, just as PDUMP did.
BENEFIT In order to get the registers, they must be saved somewhere,
which means extra code involved in debugging - which means more
chances to make an error.
TLIMIT BEING THAT THIS IS PROBABLY A MINOR CHANGE I SEE NO REASON WHY
IT CAN'T BE PROVDED VIA A PTF, THUS IT COULD BE DONE RATHER
QUICKLY.
IMPACT A BIG WASTE OF TIME TO DEBUG PROGRAMS.
REFINFO This is WAVV User Group Requirement WGxxxx022
Voting: +1=18 +2=53 no other votes
KEYWORDS SDUMP
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group
CUSTNAME ROBERT BOTSIS - Judith Jay
CATEGORY PERSONAL SYS HDW
SUBCAT DESKTOP PRODUCTS
PRODNAME PC SERVER 500 SYS/390
PRIORITY 1.8
CLASSIF L
TITLE DAT Tape Access on P/390
DESCRIPT The driver for the dat tape drive needs to support access from
both the OS/2 side and the 390 side of the Server 500 System
390 without having to reboot OS/2.
BENEFIT The dat tape drive is a valuable resource on the Server 500
System 390 that can only be half utilized now. The user must
decide which platform will own the device, OS/2 or 390 but not
both.
TLIMIT This requirement should be delivered within 6 months.
REFINFO This is WAVV User Group Requirement WGxxxx021
Voting: +1=22 +2=25 +3=9 no other votes
KEYWORDS PC Server 500 Sys/390 - VSE/ESA
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group
CUSTNAME Charles Rice - Judith Jay
CATEGORY VSE
SUBCAT GENERAL
PRODNAME VSE/ESA
PRIORITY 1.8
CLASSIF L
TITLE Have VSE Create MONITOR Records
DESCRIPT VSE, specifically the TURBO Dispatcher, collects information
about each occurance in the system. This information is lost
after each IPL or reset command. Performance
monitors/reporters are forced to use hooks or exits to sample
the state of the system, rather than being provided with the
information as it is captured. It is possible that changes to
the system and/or the performance product can cause severe
issues for the end user.
BENEFIT With the Operating System itself recording accurate
information, it is less likely that there will be a failure
with vendor code attempting to capture the data. For the user,
back end tools such as SAS could be used to report trends in
ways that may not be possible with the existing products.
Combining the VSE monitor records with VM and/or MVS records
would provide the capability to report more directly about what
is happening on the system. For example, from a VM view you
would be able to first see that a VSE guest image is causing an
issue and then drill down into the cause of the problem within
the VSE guest.
TLIMIT A timeframe is difficult to report. We would like to have the
solution quickly, but understand that development dollars are
in short supply. On the other hand, we feel that this should
not be and extremely difficult implementation - since the data
is mostly available and we would just like it permanently
recorded.
SOLUTION We would suggest that this be delivered as an option, allowing
for its use or not dependant upon vendor support. In addition,
the records should be able to be written to disk or (via
diagnose) stored with the VM MONITOR data. An SMF format or VM
MONITOR format would seem to be acceptable, with perhaps an
enhancement to RMF to enable the processing of a VSE type
record.
IMPACT We feel that as the VM/VSE synergy grows, it is important to be
able to use common tools across the platform. This feature
would allow the VM toolset to more correctly provide
information about the performance of the VSE guest.
ENVIRON It is understood that this requirement could/should be met with
the currently supported ESA versions of VSE and VM as
necessary.
VALUE With the ability to consolidate information from VM and VSE, a
more proactive pose can be taken toward performance management.
Today, VM will dispatch a VSE guest as a single task without
our ability to recognize that one of the possibly 200
partitions is causing a problem.
REFINFO This is WAVV Requirement WGxxxx019
Voting: 0=1 +1=19 +2=49 +3=7 No other votes
KEYWORDS VSE, MONITOR
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group - ADP
CUSTNAME Tom Plunkett
CADDR ONE ADP Boulevard M/S B240
Roseland, New Jersey 07068
CPHONE 201-535-7577, 201-740-8413(FAX)
CEMAIL USADJTOM @ IBMMAIL
CATEGORY TRANSACTION PROCESS.
SUBCAT CICS
PRODNAME CICS/VSE & VTAM/VSE
PRIORITY 3.0
CLASSIF S
TITLE Price Reduction on CICS and VTAM
DESCRIPT The price break on program products (Language Environment) is a
step in the right direction. Who would like to see similiar
price reductions on common code products such as CICS/VSE and
VTAM/VSE?
BENEFIT Since IBM has only a single product to support across all
mainframe environments there should be a cost savings. As
consumers of their products I would like to see these cost
savings be passed on to us.
TLIMIT ASAP
IMPACT Loss of current customers to other platforms.
REFINFO This is WAVV User Group Requirement WGxxxx018
Voting: +2=2 +3=93 no other votes
KEYWORDS Pricing CICS/VSE VTAM/VSE
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group - Dillon Companies
CUSTNAME Dave Mohrhaus
CTITLE No Title
CADDR 3980 Quebec Street
Denver, CO 80207
CPHONE (303) 393-4055
CEMAIL DMOHR@DILLONPO.COM
CATEGORY COMMUNICATION UTIL.
SUBCAT AS/400 RJE
PRIORITY 1.7
CLASSIF S
TITLE VSE/POWER NJE AS/400 Enhancements
DESCRIPT Would like a supported interface between VSE/POWER and the
AS/400. The current NJE connection is not officially supported
by IBM. This connection also does not allow for the passing of
the VSE/POWER spool file name or user data to the AS/400,
making it difficult to identify print files transferred to the
AS/400.
This connection also does not allow an AFP document on the
AS/400 to be passed back to VSE/POWER properly. When an AFP
document is passed back to VSE/POWER from the AS/400, it is put
into 80 byte segments that are no longer recognizable by
PSF/VSE.
BENEFIT Have an officially supported connection between VSE/POWER and
the AS/400 would certainly help to alleviate some uncertainty
that we have using this type of connection.
Improving the interface to allow the passing of the VSE/POWER
spool file name and user data would be very helpful in
identifying print files sent to the AS/400. This is especially
important when the AS/400 output queue is being monitored by
R/DARS-400. The monitor for R/DARS-400 requires determines
which report to store based on spool file name, user data, or
form name.
It would also be advantageous to have the ability to pass AFP
data from the AS/400 back to VSE/POWER. This would allow for
high volume re-printing to be done with PSF/VSE on larger
mainframe AFP printers, instead of a small AS/400 attached AFP
printer.
TLIMIT It would be very helpful to have this solution with the next 6
months. R/DARS-400 has been installed, and we would like to
begin to store reports on the AS/400 using the automated output
queue monitor facilities.
SOLUTION Make changes to the VSE/POWER NJE interface to pass spool file
name and user data to the AS/400.
IMPACT It would require the changing of JCL to user 4 position form
names that could be passed to the AS/400. This would also
require some sort of standard to be developed in-house to
insure that form names were not reused. Since the full R/DARS
DATA BASE : RQST - IBM INTERNAL USE ONLY PAGE: 2
report name could not be used, it would also be necessary to
set up an exit on the AS/400 to convert each form name to the
R/DARS report name.
ENVIRON VSE/ESA 1.3.4
VSE/VTAM 3.4
POWER/VSE
AS/400 3.1
REFINFO This is WAVV User Group Requirement WGxxxx017
Voting: +1=13 +2=9 +3=5 No other votes
KEYWORDS VSE/POWER NJE AS/400
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group
CUSTNAME Kevin Landin - Judith Jay
CATEGORY VSE
SUBCAT GENERAL
PRODNAME VSE/ESA
PRIORITY 1.1
CLASSIF L
TITLE Allow Global SETPARM variables outside jobs
DESCRIPT SETPARM variables and symbolic JCL provide a powerful and
flexible way to manage and control job execution. They are now
limited to statements within VSE jobs, however, so they may not
be specified on POWER JECL or JOB cards. DTRSETP allows some
circumvention by putting them in a procedure, but it must then
be executed in every job where they might be referenced and it
has the overhead of being written to disk. Global variables
such as a VM userid, VTAM node name, PNET name, etc. would be
useful if accessible without a lot of extra programming.
BENEFIT This would assist us in automating much of our operational
environment, allow us to build more intelligent JCL streams
without having to write a lot of customized REXX execs.
TLIMIT No Time LImit provided by REQUEST Author
SOLUTION Setting global symbolic variables that last across job
boundaries with a minimum of overhead to store and retrieve
them. Putting them in system GETVIS is acceptable; writing
them to disk and requiring a proc be executed (a la DTRSETP) is
not.
IMPACT We will probably consider all of the above.
ENVIRON No environment info provided
REFINFO This is WAVV User Group Requirement WGxxxx016
Voting: 0=4 +1=3 +2=21 +3=5 No other votes
KEYWORDS JCL VSE/ESA
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group
CUSTNAME Jim Thom - Judith Jay
SNAME Judith Jay
CATEGORY VSE
SUBCAT GENERAL
PRODNAME LANRES/VSE
PRIORITY 1.8
CLASSIF L
TITLE LANRES support of other NOS's
DESCRIPT LANRES only supports NOVELL networks. Any shop with a network
operating system other than Novell is precluded from taking
advantage of this new and exciting product in VSE. So LANRES
needs to support other NOS's.
BENEFIT There are many users who have other NOS's other than Novell who
are precluded from using the LANRES product. This limits the
use of VSE and the mainframe as a complete enterprise server
for these customers. By not being able to store network data
with LANRES on the mainframe this also will keep mainframe DASD
requirements from growing as quickly.
TLIMIT We would like to see this enhancement within 1 year.
SOLUTION Begin adding other network operating systems. I would suggest
to support at least native TCP/IP NFS, Banyan, Windows NT.
IMPACT We will see VSE and the mainframe losing influence as an
enterprise server.
ENVIRON LAN networks with a mainframe on the network.
REFINFO This is WAVV User Group requirement WGxxxx015 (WGxxxx020 is a
duplicate of this and not submitted)
Voting: 0=1 +1=22 +2=22 +3=12 no other votes
KEYWORDS LANRES NOS
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group
CUSTNAME Michael Basham - Judith Jay
CATEGORY VSE
SUBCAT VSE/ESA
PRODNAME LANRES/VSE
PRIORITY 2.0
CLASSIF L
TITLE LANRES/VSE for Microsoft NT LANS
DESCRIPT We are migrating from Novell Netware to Microsoft NT LANS, and
need to same functionality of LANRES in VSE to be available for
that environment that is available today in LANRES with Novell
Netware.
BENEFIT LANRES will soon no longer be a viable option for our (and many
other sites). IBM should provide LANRES participation with NT
in addition to Novell.
TLIMIT It took so long to get LANRES for Novell Netware and VSE that
business conditions changed and NT is now our direction for LAN
servers. A rather aggressive schedule is needed for NT support
also, i.e. 6 months.
SOLUTION Comparable functions and price of the existing Novell LANRES
connectivity in VSE.
IMPACT 3rd Party non-IBM solutions.
ENVIRON Currently about 13 LANS and growing. 1/2 Novell and 1/2 NT but
all expected to be NT in 6 months. 5 VSE sites
REFINFO This is WAVV User Group Requirement WGxxxx014
Voting: +1=15 +2=17 +3=14 no other votes
KEYWORDS LANRES WINDOWS_NT
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group
CUSTNAME Judith Jay