Review help

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Review help

Hercules390 - Mvs mailing list
First of all, many thanks to all of you who have contributed to this
project (MVS not specifically Review) I am particularly thinking of
Jürgen, Greg, Paul and Gerhard. Apologies if I have missed anyone
(probably). I have no professional need for MVS on a PC but it is an
interesting and refreshing change. A chance to wallow a little in
nostalgia. I am really enjoying the experience.

Secondly, is there an up-to-date user guide for Review somewhere - I
have not found anything more recent than version 36 (IIRC). I have never
used the "Official" ISPF ever (not that Review is a copy, I know but it
does resemble it in some ways). Most of the MVS sites that I had
anything to do with, ran Software AG's TP monitor Com-Plete. Those that
did use TSO/ISPF would not let us mere software vendors anywhere near a
monitor so I never got to use it.

One problem, actually an issue rather than a problem with Review, is on
panel 3.2 (for one), there is a field marked "other datasets" and a
"volume" field. If I enter something like "SYS1.PARMLIB" in the other
field it responds with "dataset not found". If I also put  MVSRES in the
volume field, I get "dataset not on volume". This happens with any
dataset. Panel 3.4 works as I would expect, little that I know.

Greetings from a swelteringly hot Kwazulu-Natal in South Africa. 34+ deg
C today.

Bill Turner

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Review help

Hercules390 - Mvs mailing list
Hello Bill,

IMO:

if you enter filenames there without apostrophes, then your TSO id will be
added to it, that is, not SYS1.PARMLIB is searched, but USERID.SYS1.PARMLIB
(whatever your TSO USERID is). You have to enter 'SYS1.PARMLIB' to get the
desired result. For convenience, you can omit the second apostrophe on
most fields

(this is how today's ISPF works, I don't know Review).

3.4 is different ...

Kind regards

Bernd
Southern Germany (Nuremberg), 2 degree C


Am 08.03.2017 um 06:22 schrieb William D ASM [hidden email] [H390-MVS]:

>
> First of all, many thanks to all of you who have contributed to this
> project (MVS not specifically Review) I am particularly thinking of
> Jürgen, Greg, Paul and Gerhard. Apologies if I have missed anyone
> (probably). I have no professional need for MVS on a PC but it is an
> interesting and refreshing change. A chance to wallow a little in
> nostalgia. I am really enjoying the experience.
>
> Secondly, is there an up-to-date user guide for Review somewhere - I
> have not found anything more recent than version 36 (IIRC). I have never
> used the "Official" ISPF ever (not that Review is a copy, I know but it
> does resemble it in some ways). Most of the MVS sites that I had
> anything to do with, ran Software AG's TP monitor Com-Plete. Those that
> did use TSO/ISPF would not let us mere software vendors anywhere near a
> monitor so I never got to use it.
>
> One problem, actually an issue rather than a problem with Review, is on
> panel 3.2 (for one), there is a field marked "other datasets" and a
> "volume" field. If I enter something like "SYS1.PARMLIB" in the other
> field it responds with "dataset not found". If I also put MVSRES in the
> volume field, I get "dataset not on volume". This happens with any
> dataset. Panel 3.4 works as I would expect, little that I know.
>
> Greetings from a swelteringly hot Kwazulu-Natal in South Africa. 34+ deg
> C today.
>
> Bill Turner
>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Review help

Hercules390 - Mvs mailing list
In reply to this post by Hercules390 - Mvs mailing list
---In [hidden email], <bturnersa@...> wrote :

> First of all, many thanks to all of you who have contributed to this
> project (MVS not specifically Review) I am particularly thinking of
> Jürgen, Greg, Paul and Gerhard. Apologies if I have missed anyone
> (probably).

Thanks for the credit, but I'd like to
make it clear that the products I
release (and noting that it was
Scott Cosel who released the most
recent versions of MVS/380) are only
possible because of a myriad of
others who provide vital information
I need to do that work. As just one
example, somitcw telling me about
IDCAMS REPRO to convert
RECFM=U into RECFM=V
and vice-versa.

Below is the credit just for the GCCMVS
product, and even that is incomplete.

BFN. Paul.




Everyone who worked on GCC in areas besides i370
  and to the people out there who contribute the
  odd fix that they developed.
Jan Stein for the original i370 machine definition
Dave Pitts for doing the port to OS/390 USS,
  without which the further work could not have
  been done.
Linas Vepstas for a slew of bug fixes and enhancements
  made during his port of Linux to S/370.
Paul Edwards for doing the port to native (ie
  non-USS) MVS 3.8, MVS/XA, OS/390, Z/OS, MVS/380
  as well as getting GCC to be able to compile
  itself on the mainframe (previously it was
  only compilable by IBM's C compiler).
Phil Roberts for testing & debugging & releasing
  the native MVS port created by Paul Edwards. The
  product wouldn't exist without Phil's work either.
Dave Wade for fixing the last compiler bug that
  was preventing GCC from compiling itself on the
  mainframe, and also for doing the VM/CMS port.
  And various other bug fixes and improvements to
  PDPCLIB as well.
Chris Langford and Dave Jones for the prolog/epilog
  macros.
Dave Edwards (RIP) for doing the MUSIC/SP port and
  fixing various bugs in PDPCLIB in the process.
Tim Pinkanawa for writing the HTML documentation.
Tim Holloway for figuring out where to put the code
  to get the static function names unique so that
  the final problem stopping the compiler from
  being C90 compliant was fixed.
Robert O'Hara for getting EPLIST support in PDPCLIB
  working on CMS and providing the mods to VM/380
  required to get 31-bit GCCCMS binary compatible
  between VM/380 and z/VM.
Gerhard Postpischil for providing the mods to MVS/380
  required to get 31-bit GCCMVS binary compatible
  between MVS/380 and z/OS so that we could build
  GCCMVS on a free system. Also for the final functions
  missing in PDPCLIB for C90 conformance for MVS and
  for the virtual rewrite of mvssupa.asm.
Scott Cosel for the XMIT JCL which enabled a nice
  package to be produced for z/OS users. Also for
  producing a real 31-bit z/OS executable using
  GCCMVS on z/OS and putting that in XMIT format to
  truly test MVS/380. Also for other testing.
Tony Harminc for assistance in getting integer divide
  working properly.
Ulrich Weigand for providing direction on tying up some
  loose ends, especially getting rid of some warnings from
  gencomp.
Fausto Saporito for his work on making the MUSIC/SP port
  native.
Fran Hensler, Bruce Smith, Bill Carlborg, Louis Millon,
  Michel Beaulieu and others for assistance and code
  for the z/VSE port.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Review help

Hercules390 - Mvs mailing list
On 08/03/2017 09:05, [hidden email] [H390-MVS] wrote:

>
> ---In [hidden email], <bturnersa@...> wrote :
>
> > First of all, many thanks to all of you who have contributed to this
> > project (MVS not specifically Review) I am particularly thinking of
> > Jürgen, Greg, Paul and Gerhard. Apologies if I have missed anyone
> > (probably).
>
> Thanks for the credit, but I'd like to
> make it clear that the products I
> release (and noting that it was
> Scott Cosel who released the most
> recent versions of MVS/380) are only
> possible because of a myriad of
> others who provide vital information
> I need to do that work. As just one
> example, somitcw telling me about
> IDCAMS REPRO to convert
> RECFM=U into RECFM=V
> and vice-versa.
>
> Below is the credit just for the GCCMVS
> product, and even that is incomplete.
>
> BFN. Paul.
>
Thanks Paul - I understand all that and apologize for not making that
clearer. I just have not been as close to the project as you and was not
aware of all the people that have contributed. I stand corrected (and
humbled). Never mind, I just wanted to thank the ones that have directly
helped me in some way.
All the best
Bill
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Review help

Hercules390 - Mvs mailing list
In reply to this post by Hercules390 - Mvs mailing list
On 08/03/2017 08:09, Bernd Oppolzer [hidden email] [H390-MVS]
wrote:

>
> Hello Bill,
>
> IMO:
>
> if you enter filenames there without apostrophes, then your TSO id
> will be
> added to it, that is, not SYS1.PARMLIB is searched, but
> USERID.SYS1.PARMLIB
> (whatever your TSO USERID is). You have to enter 'SYS1.PARMLIB' to get
> the
> desired result. For convenience, you can omit the second apostrophe on
> most fields
>
> (this is how today's ISPF works, I don't know Review).
>
> 3.4 is different ...
>
> Kind regards
>
> Bernd
> Southern Germany (Nuremberg), 2 degree C
>
Ah yes of course - that can be turned off with the ACCOUNT command I
seem to remember. No need of course if one knows what is required.
Still looking for a Review user guide if it exists.
Thanks very much
Bill
<SNIP>

> Secondly, is there an up-to-date user guide for Review somewhere - I
>>
>> have not found anything more recent than version 36 (IIRC). I have never
>> used the "Official" ISPF ever (not that Review is a copy, I know but it
>> does resemble it in some ways). Most of the MVS sites that I had
>> anything to do with, ran Software AG's TP monitor Com-Plete. Those that
>> did use TSO/ISPF would not let us mere software vendors anywhere near a
>> monitor so I never got to use it.
>>
>> One problem, actually an issue rather than a problem with Review, is on
>> panel 3.2 (for one), there is a field marked "other datasets" and a
>> "volume" field. If I enter something like "SYS1.PARMLIB" in the other
>> field it responds with "dataset not found". If I also put MVSRES in the
>> volume field, I get "dataset not on volume". This happens with any
>> dataset. Panel 3.4 works as I would expect, little that I know.
>>
>> Greetings from a swelteringly hot Kwazulu-Natal in South Africa. 34+ deg
>> C today.
>>
>> Bill Turner
>>
>
>


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Review help

Hercules390 - Mvs mailing list
On 2017-03-08 10:16 PM, William D ASM [hidden email] [H390-MVS] wrote:
> Ah yes of course - that can be turned off with the ACCOUNT command I
> seem to remember. No need of course if one knows what is required.
> Still looking for a Review user guide if it exists.
ACCOUNT?

Perhaps you mean
PROFILE NOPREFIX
??

No such user guide exists (AFAIK) though it has been suggested to me
that I should write a manual for it.
Of course, time spent writing doco is time not spent writing code.
:)

If I had written a manual, I doubt I would have covered this point,
though.  To me it comes under basic TSO user training, and not
particularly specific to REVIEW.  Of course, my assumption would have
been that most users had used SPF or ISPF and so would be familiar with
that aspect, but I gather from what you said earlier that in your case
my assumption would have been wrong.

Sometimes I think about writing a REVIEW/RFE manual, but how it should
be organised is not clear to me, so I never start it.

The best I can suggest is to read the TSO help members which I try to
keep up to date.  I think I have mentioned most of the little tricks I
know in there, such as
1. issuing NEWTOP to deactivate "fast path" to be used when REVIEW's
assumption that a the location of a remote record can be calculated
based on the record number is incorrect.
(You can also use NEWTOP to jump over e-o-f markers to see any residual
data in the data set's extents.)
2. Issuing HEX ON, RIGHT MAX then HEX OFF to see the TTR (block address)
or RBA (for VSAM) from which each record came.
3. Using FMTPRT ON/OFF to control whether you want trailing blanks
copied on a COPYOUT command.

Also, you will find out about wacky commands I've just made up such as
SETUNZ, RTF, and the FMTPRT and NEWTOP already mentioned.  R47.0 also
added some extra hex formats which are probably of dubious usefulness.

Cheers,
Greg


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Review help

Hercules390 - Mvs mailing list
- - - In [hidden email], <greg.price@...> wrote:
- - - beginning snipped - - -
> No such user guide exists (AFAIK) though it has been suggested to
>me that I should write a manual for it.
> Of course, time spent writing doco is time not spent writing code.
> :)
- - - ending snipped - - -

A manual would be nice but can never be found when needed and
you need to scan many pages to get little information.

A manual would let me know if AUTOSAVE works like other editors.
That is that if there have been changes, "END" would prompt for
either a destructive overwrite or cancel the new changes.

I also didn't have Review 'HELP' in my USRLOGON CLIST so
that wasn't working but something is there now.
No manual and no HELP was not fun.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Review help

Hercules390 - Mvs mailing list
In reply to this post by Hercules390 - Mvs mailing list
On 08/03/2017 16:04, Greg Price [hidden email] [H390-MVS] wrote:

>
> On 2017-03-08 10:16 PM, William D ASM [hidden email] [H390-MVS]
> wrote:
> > Ah yes of course - that can be turned off with the ACCOUNT command I
> > seem to remember. No need of course if one knows what is required.
> > Still looking for a Review user guide if it exists.
> ACCOUNT?
>
> Perhaps you mean
> PROFILE NOPREFIX
> ??
>
I did actually - oh well -  maybe a TSO course might be an idea....
>
>
> No such user guide exists (AFAIK) though it has been suggested to me
> that I should write a manual for it.
> Of course, time spent writing doco is time not spent writing code.
> :)
>
Understood - been there.
>
> If I had written a manual, I doubt I would have covered this point,
> though. To me it comes under basic TSO user training, and not
> particularly specific to REVIEW. Of course, my assumption would have
> been that most users had used SPF or ISPF and so would be familiar with
> that aspect, but I gather from what you said earlier that in your case
> my assumption would have been wrong.
>
Yes - the only time I had previously used TSO was during a first time
install of MVS at a government site at Ulundi in rural Kwazulu-Natal
using install tapes that had been previously prepared by government
system admins with totally wrong dataset names for Com-Plete. This was
10pm on a Friday. Not a soul answering phones. Fortunately we found a
manual that had mentioned the IBMUSER  userid and to type "HELP". Took
us about an hour but finally got the datasets renamed and Com-Plete up.
Never used TSO since then until I was introduced to this. Am really
enjoying it.

>
> Sometimes I think about writing a REVIEW/RFE manual, but how it should
> be organised is not clear to me, so I never start it.
>
> The best I can suggest is to read the TSO help members which I try to
> keep up to date. I think I have mentioned most of the little tricks I
> know in there, such as
> 1. issuing NEWTOP to deactivate "fast path" to be used when REVIEW's
> assumption that a the location of a remote record can be calculated
> based on the record number is incorrect.
> (You can also use NEWTOP to jump over e-o-f markers to see any residual
> data in the data set's extents.)
> 2. Issuing HEX ON, RIGHT MAX then HEX OFF to see the TTR (block address)
> or RBA (for VSAM) from which each record came.
> 3. Using FMTPRT ON/OFF to control whether you want trailing blanks
> copied on a COPYOUT command.
>
> Also, you will find out about wacky commands I've just made up such as
> SETUNZ, RTF, and the FMTPRT and NEWTOP already mentioned. R47.0 also
> added some extra hex formats which are probably of dubious usefulness.
>
> Cheers,
> Greg
>
Thanks very much for all that.
All the best
Bill
>
>


Loading...