Depending on your clients willingness to change, you could use REXX/CICS. It has a VM like editor. You can roll your own SUBMIT command. It is *free* with CICS.
On Wed, Feb 5, 2020, 06:14 Bernd Oppolzer <[email protected]> wrote: > After working now two days with it, what strikes me most is the absence > of a SAVE command. > Every line you change (or delete !) is changed on the file even without > SAVE, same goes for deletions, > and there is no recovery (no other than saving the member before you > begin or restoring an older > version for the CA master lib). > > And some of the prefix commands are different from ISPF: Prefix command > A means insert of a blank line > and prefix I does insertions of lines which are in a buffer (like CUT > ... PASTE). CC ... CC inserts lines into > this buffer, but the buffer is not emptied prior to CC ... CC. If you > want the buffer to be emptied, > you have to use CCD (or CD, for a single line). > > I've worked with MVS for the last 25 years, so I will have a hard time > in the next weeks :-) > But I've done VSE before, and today I recalled how to do F F5 (or PFLUSH > F5) to free a locked partition > in VSE ... I've used this before in the late 1990s :-) > > F F5 can be done from with VOLLIE using the OPE command :-) > VOLLIE even shows the status of the partitions and the operator console. > > Kind regards > > Bernd > > > Am 04.02.2020 um 03:09 schrieb Wayne Bickerdike: > > That's a blast from the past. > > It does run as a CICS transaction (Normally OLLE). > > > > It is 1000% better than the IBM VSE offering (name escapes me). > > > > In architecture it's not unlike ROSCOE, runs very lean and mean. All > > the members are contained within a single VSAM cluster which is > > formatted and then has 3 char lib prefixes and 8 char names similar to > > a PDS. eg JCL.MASTJOB1. > > > > It also has a crude form of security, defined in a macro assembler > > module. This determines what you can see and do. A very naughty > > programmer substituted his own version and when we found out, I > > substituted yet another module that blasted ***violation*** on the > > console. The guy in question (Kevin Parker where are you now?) crapped > > his pants when he realised he'd been rumbled. Had an entertaining > > dressing down meeting with him. > > > > >From memory, I belive you use the "l" command (list) to bring up a > > member in an editor panel. > > > > It has a submit command (I think sub?) and has access to the Power > > spool to fetch output. > > > > It's been 30 years since I last saw Vollie :) > > > > On 2/4/20, Bernd Oppolzer <[email protected]> wrote: > >> great, thank you, I will have to ask my customer, if we can have access > >> to this site. > >> Thanks, kind regards > >> > >> Bernd > >> > >> > >> Am 03.02.2020 um 20:51 schrieb Frank Swarbrick: > >>> I don't have a Broadcom logon, but did you try this page? > >>> > https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-miscellaneous/legacy_bookshelves_and_pdfs/bookshelves_and_pdfs/bookshelves/ca-vollie-for-z-vse.html > >>> > >>> ________________________________ > >>> From: IBM Mainframe Discussion List <[email protected]> on > behalf > >>> of Bernd Oppolzer <[email protected]> > >>> Sent: Monday, February 3, 2020 11:25 AM > >>> To: [email protected] <[email protected]> > >>> Subject: Manuals for CA-VOLLIE? > >>> > >>> In my new project assignment, I have to use a tool called VOLLIE (from > >>> CA), which is used to modify (edit) > >>> VSE libraries and prepare compile and test jobs for VSE and COBOL-CICS > >>> programs etc. > >>> > >>> No VM in this installation. VOLLIE seems to be a CICS transaction. > >>> > >>> Is there a manual for CA-VOLLIE, which can be shared, for example PDF > >>> format? > >>> No match when using the well-known search engines. > >>> > >>> Thanks and regards > >>> > >>> Bernd > >>> > >>> ---------------------------------------------------------------------- > >>> For IBM-MAIN subscribe / signoff / archive access instructions, > >>> send email to [email protected] with the message: INFO IBM-MAIN > >>> > >>> ---------------------------------------------------------------------- > >>> For IBM-MAIN subscribe / signoff / archive access instructions, > >>> send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
