Second group of WAVV 1995 IBM Requirements
CATEGORY PERSONAL SYS HDW
SUBCAT SERVER PRODUCTS
PRODNAME PC SERVER 500 SYS/390
PRIORITY 2.2
CLASSIF L
TITLE PC Server 500 S/390 Enhancements
DESCRIPT The PC Server 500 S/390 Future enhancements and expandability.
BENEFIT The PC Server 500 S/390 (we prefer the P/390 acronym by far...)
is an outstanding piece of architecture! It should continue to
be enhanced boldy and to realize it's true potential. It can
indeed be a MAJOR client/server viable product for our
environment and others if upper management believes that IBM
truely will let it loose to it's true potential.
TLIMIT We can not tell the future of the box, which makes planning
impossible (dangerous, nay sometimes fatal in this day and
age..). Statements on what is coming should be made and an as
new equipment comes out VSE should support it.
SOLUTION Faster processors, PCI and access to existing mainframe DASD
(3380/3390 etc) should all be supported as should larger newer
versions of IBM servers as they become available.
IMPACT We don't see these boxes cutting revenue to IBM at all, but
possibly saving multiple VSE sites with IBM in our organization
and others. It is the first time in 5 years that upper
management has some enthusiasm for VSE again. It a future
upgrade path is available and IBM flaunts this great technology
with aggressive marketing, we think a VSE revival is still
feasible.
ENVIRON 5 VSE sites (11 more at parent company). Potential new use in a
new location (being evaluated) and if a future (good one that
is) is defined potential use for other new applications and
distributing workload at existing sites.
VALUE Future of VSE is defined as stabalized at our parent company
and in doubt for us, this can make the difference of life or
death possibly.
REFINFO This is WAVV User Group Requirement WGxxxx013
Voting: 0=1 +1=5 +2=22 +3=11 No other votes
KEYWORDS P/390 PC Server 500 S/390 Enhancements
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group
CUSTNAME Ed Puskas - Judith Jay
CATEGORY TRANSACTION PROCESS.
SUBCAT CICS
PRODNAME CICS/VSE
PRIORITY 1.7
CLASSIF L
TITLE CICS Internet Access for VSE
DESCRIPT CICS Internet (and Internet tools/protocols) Connectivity to
VSE!
BENEFIT Some announcements were made by IBM on CICS connectivity with
the Internet in other platforms (MVS etc.). Once again VSE was
ignored. VSE users and companies have the same requirements as
any other in this area. The same Internet/CICS interfaces would
be very valuable for VSE and VM users as well.
TLIMIT We are starting to use Internet tools internally to build
multiple company Web servers. Most sites also have VSE and
CICS. To access data easily through the Internet tools is
essential and right now VSE is the only platform that can't
not. The CICS/Internet connectivity for MVS sounds like a good
start to bring VSE participation into the Internet world as
well.
SOLUTION Internet Access to CICS very similar to the latest
announcements in other IBM platforms.
IMPACT VSE is still lagging behind badly compared to other operating
systems in keeping up with newer technology. VSE sites can no
longer afford to wait several years to catch up. We have the
same business needs and pressures as companies on the other
operating systems.
ENVIRON VSE to NT and Unix Web servers. TCP/IP and PPP protocols. VSAM,
DLI and Adabas file systems.
REFINFO This is WAVV User Group Requirement WGxxxx012
Voting: -1=1 0=2 +1=25 +2=33 +3=9 No other votes
KEYWORDS VSE Internet Participation - CICS/VSE
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group
CUSTNAME Ed Puskas - Judith Jay
CATEGORY TRANSACTION PROCESS.
SUBCAT MQSERIES
PRODNAME MQSERIES/VSE
PRIORITY 1.7
CLASSIF L
TITLE MQ Series Enhancements for VSE
DESCRIPT We have many requirements for client/server applications
running remotely to send and receive data to VSE. Messaging is
an excellent reliable client/server access vehicle in almost
all platforms. We would like to use MQ Series but it has not
been enhanced like the MVS, OS/2 and AIX versions. We need the
same enhancements in VSE for MQSeries to make it a viable
product.
BENEFIT IBM has told us that they are waiting to see how many people
buy MQ Series in VSE to determine if it will be upgraded in
VSE. We believe this is a product that would sell much better
if the enhancements are in place, since many sites like us are
waiting to see if you enhance it, because we don't want to buy
a dead minimal function product.
TLIMIT Most sites can't afford to wait long when infrastructure pieces
are needed. For us we rate the need as being within 6 months.
SOLUTION New versions of the product soon with the same enhancements as
the other operating systems, because we have the same need.
IMPACT Third party products, more bad feelings by upper management
that VSE may not be strategic.
ENVIRON Multiple VSE sites needing to access HP UX 10 boxes to start.
SCO, AT&T, and AIX Unix platforms also are futures as well as
NT.
VALUE Messaging makes sense in WAN client/server
REFINFO This is WAVV User Group Requirement WGxxxx011
Voting: 0=2 +1=23 +2=14 +3=8 No other votes
KEYWORDS Messaging for VSE
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group
CUSTNAME Ed Puskas - Judith Jay
CATEGORY VM
SUBCAT GENERAL
PRODNAME VM/ESA
PRIORITY 2.0
CLASSIF L
TITLE VM/VSE Synergy should be more than just a cute slogan
DESCRIPT 1. VSAM ESDS/SAM files increasingly used in VSE, but cannot be
accessed from VM/CMS.
2. No native VSE library access, even read-only, from VM/CMS.
3. No native VM file system access, even read-only, from VSE.
4. Even though sharing VSE/VSAM code, VM and VSE cannot share
VSAM catalogs read/write, resulting in a multiplicity of
catalogs and a mess trying to manage them.
BENEFIT VM had better support for "DOS" 20 years ago than it has for
VSE today. With MP support for VSE, the business justification
for VM is becoming increasingly more difficult to make. Unless
IBM provides more functionality for VSE guests in VM, those
guests are likely to seek refuge elsewhere.
TLIMIT It should have been done years ago.
SOLUTION Since VSE users can now put their VSE lock file in VM, that
lock file could serve as a mechanism by which VM could allow
the sharing and queuing of resources across both platforms.
Those resources could include read/write access to a VSAM
catalog, as a minimum. There is no reason why each platform
shouldn't provide read-only access to the other's file and
library structures, or why the ESDS/SAM feature is disabled in
VM.
IMPACT There are software vendors who provide some of these functions.
The more likely scenario is that we will drop VM.
REFINFO WAVV User Group Requirement - WGxxxx010
Voting: 0=3 +1=13 +2=29 +3=14 No other votes
KEYWORDS VM, VSE, VSAM, DITTO - VM Synergy
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group
CUSTNAME Jim Thom - Judith Jay
CATEGORY VSE
SUBCAT VSE/POWER
PRODNAME VSE/POWER
PRIORITY 2.0
CLASSIF L
TITLE POWER should drop 1R33D CORRECT FULL STATEMENT
DESCRIPT When POWER finds an error in an LST JECL statement, it writes
the following message on the system console: 1R33D CORRECT
FULL STATEMENT. The problem is 1. If the original statement
had two or more lines, only the last line is displayed, while
the error could be on the first; 2. It hangs the partition
waiting for the operator to respond, and 3. The operator
usually doesn't have a clue how to respond anyway, but just
hits enter.
BENEFIT Hanging a batch partition up for whatever time it takes the
operator to notice it and respond is not a good idea. Other
components of VSE (JCANCEL, ACANCEL options) have addressed the
need to keep the system jobs flowing. The operator response
will usually allow the job to run, but lose or misdirect its
LST output.
TLIMIT No Time Limit Provided by Request Author
SOLUTION 1. Pick up the JCANCEL option and use it for JECL errors.
2. Allow a new option for POWER generation and/or startup.
IMPACT Better throughput, less operator intervention.
REFINFO WAVV User Group Requirement WGxxxx009
Voting: -1=4 0=33 +1=34 +2=4 +3=2 No other votes
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group
CUSTNAME Jim Thom - Judith Jay
CATEGORY VSE
SUBCAT GENERAL
PRIORITY 2.3
CLASSIF L
TITLE Change VOLID for VSE system residence volume
DESCRIPT Request that IBM change the volume id for the system residence
volume from DOSRES to VSERES.
BENEFIT Years ago Wolfgang Vogt requested the user groups to cease
using DOS references in names and commence substituting VSE in
its place. This suggestion was taken back to the local user
group and it was decided that the name MN DOS Users Group would
remain until IBM changed the name of DOSRES to VSERES.
Minnesota DOS Users Group..
TLIMIT With the next release.
IMPACT A substantial amount of time will be saved by the membership of
the Minnesota DOS Users Group if they are no longer approached
by PC DOS users asking for assistance with their problems.
REFINFO This is WAVV User Group Requirement WGxxxx008
VOTING: +1=6 +2=52 3+=36 No other votes
INITBY CUST
CNTRYCD 600
COMPANY WAVV USER GROUP REQUIREMENT
CUSTNAME Judith Jay
CTITLE No Title
CADDR No Address
CATEGORY VSE
SUBCAT VSE/AF
PRODNAME VSE/ESA
PRIORITY 1.3
CLASSIF S
TITLE SDUMP MACRO ENHANCEMENT
DESCRIPT SDUMP MACRO PROVIDES NO WAY TO, VIA OPTIONS, TO PRODUCE A DUMP
TO SYSLST OR TO PRINT THE CONTENTS OF THE REGISTERS (IE. GP,
AC, ETC.) IF A PARTITION WAS STARTED, SUCH AS CICS, AND IT WAS
DESIRED THAT THE OUTPUT PRODUCED BY SDUMP WAS TO BE WRITTEN TO
SYSLST RATHER THAN THE DUMP FILE THE PARTITION HAS TO BE SHUT
DOWN, THE // OPTION STATEMENT CHANGED AND THE PARTITION
RESTARTED. IT WOULD BE MUCH SIMPLIER TO PROVIDE AN OPTION, IN
THE SDUMP MACRO, TO OVERRIDE THE // OPTION STATEMENT SO THAT THE
DUMP OUTPUT IS DIRECTED TO SYSLST.
ALSO, WHEN DEBUGGING A PROGRAM ESPECALLY AN ASSEMBLER
PROGRAM, IT'S MOST HELPFUL IF THE CONTENTS OF THE REGISTERS ARE
CAN BE PROVIDED. WITHOUT AN OPTION, IN THE SDUMP MACRO. IT'S
NECESSARY TO STORE THE REGISTERS AND BASICALLY PRODUCE TWO
DUMPS, ONE DUMPING TE CONTENTS OF THE SAVED REGISTER AND THE
OTHER DUMPING THE STORAGE AREA DESIRED. SEEMS THIS IS
UNCESSARY, ESPECIALLY SINE THE OLD PDMP MACRO DID IT WTHOUT THE
USER HAVING TO DO ANYTHING.
BENEFIT BY PROVIDING OPTIONS TO PRODUCE THE DUMP ON SYSLST AND TO PRINT
THE CONTENTS OF THE REGSTERS SAVES TIME BECAUSE 1). THE DUMP
DOESN'T HAVE TO BE PRINTED LATER BY THE DUMP MANAGEMENT PROGRAM
THUS PROVIDING QUICKER DEBUGGING 2). PRINTING THE CONTENTS OF
THE REGISTERS, WITHOUT ADDING EXTRA CODE TO SAVE THEM, SAVES
INVOKING THE DUMP TWICE AND ALSO FACILITATES QUICKER DEBUGGING.
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.
SOLUTION AS ACCEPTABLE SOLUTION WOULD BE TO PROVIDE EXTRA OPERANDS ON
THE SDUMP MACRO.
IMPACT A BIG WASTE OF TIME TO DEBUG PROGRAMS.
ENVIRON VSE/ESA
ENDVAL 4
REFINFO This is WAVV User Group requirement WGxxxx006
Voting:_ -1=1 0=11 +1=21 +2=13 no other votes
KEYWORDS SDUMP
INITBY CUST
CNTRYCD 600
COMPANY WAVV User Group
CUSTNAME ROBERT BOTSIS - Judith Jay IBM
CATEGORY VSE
SUBCAT VSE/POWER
PRODNAME VSE/POWER
PRIORITY 1.2
CLASSIF L
TITLE POWER should limit the number of SAS tasks
DESCRIPT Unlike device or partition tasks started at IPL or by operator
command, SAS tasks (Spool Access Subsystem) are not limited in
number by anything other than the common sense of programmers
who write programs to initiate them. When a program gets stuck
in a loop starting SAS tasks, it fills up POWER's GETVIS, hangs
the VSE system and forces a re-IPL. This is called a feature.
BENEFIT Our users get uptight about unscheduled IPL's.
TLIMIT Since it addresses VSE system integrity, it should be resolved
quickly, which translates into one or two years.
SOLUTION POWER generation and startup parameters should allow
specification of a maximum number of SAS tasks, both globally
and by individual partition. The default should be small, like
12 and 6, respectively.
IMPACT If not implemented, the loophole will remain and we will be at
the mercy of those who write the code to have it work perfectly
the first time it runs.
ENVIRON VSE/ESA 1.3.2 and VSE/POWER.
REFINFO This is WAVV User Group Requirement WGxxxx005
Voting: -2=1 -1=11 0=38 +1=9 +2=1 no other votes
INITBY CUST
CNTRYCD 600
CLARIFY Update entered by Judith Jay 19951201 16:03:40
Voting reported incorrectly (WAVV voting) please note this
correction:
-1=1 0=11 +1=38 +2=9 +3=1 is correct.
COMPANY WAVV User Group
CUSTNAME Judith Jay
CATEGORY VSE
SUBCAT GENERAL
PRODNAME VSE/ESA
PRIORITY 1.6
CLASSIF T
TITLE VSE/ESA 2.1 console support for type 2 II user
DESCRIPT Reduce the amount of time spent setting up and performing
routine database maintenance. Prevent potential mistakes in
setting up routine database reorgs/maintenance activities.
BENEFIT The type 2 users are program developers who have a need to view
all messages displayed in order to diagnose production programs
that have cancelled. MIS Policy prevents Developers from having
access to entering commands.
TLIMIT The urgency is immediate as Development staff are working on a
critical application that is ongoing and will take app. one
year. The development staff are not in the same building as the
data center so they are not able to view the console directly.
SOLUTION The solution is to provide a similar profile capability as was
provided in prior releases of VSE/ESA.
IMPACT The impact is that i would have to find an alternative console
support package. We have not had the need in the past and so
have not budgeted for that type of package.
For the Development staff this means constant phone calls to
the data center requested what is displayed on the console. Or
providing hardcopy of the console.
ENVIRON Environment is VSE/ESA 2.1.0 running native on 4381-91E.
Staff impacted is the Applications Development staff and the
Operations staff.
VALUE The impact to the business is delays in the development cycle.
The end user productivity would be greatly enhanced in that the
developers are not having to rely or wait for Opps staff to
provide either telephone support or hardcopy of the console.
This also keeps existing MIS security policies in place
concerning master console access.
REFINFO This is WAVV USER GROUP Requirement: WGxxxx004
Voting: -1=9 0=25 +1=18 +2=6 no other votes
INITBY CUST
CNTRYCD 600
CLARIFY Update entered by Judith Jay 19951201 16:02:24
Voting reported incorrectly. Please make note of this
correction (WAVV voting)..
0=9 +1=25 +2=18 +3=6
COMPANY Massachusetts Medical Society
CUSTNAME Terry Spaulding
CTITLE no title
CADDR 1440 Main st.
Waltham Ma. 02154
CPHONE 617-893-3800 x-1113
CEMAIL TLS_MIS_1440@MMSPO.MMS.ORG
CATEGORY TRANSACTION PROCESS.
SUBCAT CICS
PRODNAME CICS/VSE
PRIORITY 2.0
CLASSIF L
TITLE CICS cmd level exit must retain functions of macro level exit
DESCRIPT The CICS command level exits do not have all the functions that
were previously existed with the macro level exits. Example:
The interval control exit for macro level would allow you to
change the request type before returning from the exit. In
this way a terminal oriented request could be disassociated
from the original request.
BENEFIT IBM in the past has made statement of directions that they
would not take function away from the user. The current
implementation of command level only exits seem to be reversing
that implied direction. This will force the user to either
look at other products or some other alternative to solve a
problem that presently does not exist.
TLIMIT This must be delivered before IBM forces command level only
upon us.
ENVIRON CICS/VSE for VSE/ESA (2.2 and 2.3 of CICS/VSe)
VALUE As a user of CICS I cannot afford to loose the functions that
currently exist.
REFINFO This is WAVV User Group requirement # WGxxxx002
VOTING information: -3=1 0=21 +1=46 +2=5 no other votes
INITBY CUST
CNTRYCD 600
CLARIFY Update entered by Judith Jay 19951201 16:00:42
Voting incorrect in original submission.
-2=1 +1=21 +2=46 +3=5 is the correct WAVV voting. Please make
note!
COMPANY WAVV User Group - No customer Name
CUSTNAME Judith Jay