开云体育

Look for gc28-0629-1 on bitsavers. I think it’s the ibm/370/os_vs2/release 3.7 directory. Read the section on pre-prompt exit

开云体育

Thanks to all who responded to my query about logon procs.? I was able to use the ACCOUNT command to add the ISPLOGON proc to my userid in SYS1.UADS.? (That ACCOUNT command ought to be a prime candidate for the computer command with the most obtuse syntax ever devised!)

While we are on the subject of logon procs, I once again have access to a real IBM MVS system running z/OS.? When I logon to that system, I enter my userid and then I am presented with the following panel:

The values displayed in those fields are remembered from one logon session to the next.

Is there any way our MVS 3.8j system can be configured to operate like that?? Can it be done with some VTAM programming or some such?
(Since the title at the top of that screen says "TSO/E LOGON" I'm guessing that the answer is "no".)

Charles Bailey

开云体育

You will need to use the ACCOUNT command from either HERC01 or HERC02 as they have OPER privileges.

Just a small nitpick - the ACCT privilege is required by a user ID to issue the ACCOUNT command.

For those who aren't long term TSOers, the 4 general privilege settings associated with a TSO user ID are:

• ACCT / NOACCT - controls the ability to use the ACCOUNT command.
• OPER / NOOPER - controls the ability to use the OPERATOR (or OPER for short) command.
• JCL / NOJCL - controls the ability to use the FIB (foreground initiated background) commands of STATUS (ST), SUBMIT (SUB), OUTPUT (OUT) and CANCEL.
• MOUNT / NOMOUNT - controls whether the TSO session will issue a console mount request when an attempt is made to allocate a data set on an unmounted volume.? These mount requests are actually IEF455D WTOR messages meaning that the operator has the option of replying NO to deny the allocation request.

(BTW, commands such as ACCOUNT, OPERATOR, OUTPUT, TEST and EDIT (and PDS which is not from IBM) are examples of commands which process subcommands.? When these commands are active, the mode prompt is not READY but the name of the command, except for when EDIT is in input mode, where the prompt is INPUT.)

Having the MOUNT attribute means that it is fairly easy to browse tape data sets, especially if they are cataloged because you don't even have to supply the UNIT and VOLUME, nor contrive to supply the file sequence number.

The REVTAPE CLIST uses the ALLOCATE command to supply the file sequence number.

Yes, REVIEW does provide the same up and down scrolling control for tape data sets as it does for DASD data sets.? Have fun trying to scroll up to a previous volume - this used to not work when it would apply TTRs from earlier volumes to the current volume, but these days it may request the operator to re-mount the first volume - can't say for sure because I haven't tried it.? (The last time I regularly used tapes was 2002.)

Of course, having the MOUNT attribute means that if you mistype the volume serial you'll often end up with a hanging mount request, so on real systems where I am not the operator I like to run with NOMOUNT most of the time.? If I ever need MOUNT I just zap the bit on for that session.? IM VB has the MNT and NMNT commands to facilitate this.

Cheers,
Greg

开云体育

Charles,

This is my fault for not documenting how to authorize a user to use a new logon proc, and I will update the documentation in the next release

.

As a good practice, the key SYS1 datasets such as 'SYS1.PROCLIB' are generally reserved for IBM provided materials, I recommend you place the proc in 'SYS2.PROCLIB' which exists for this purpose.

Wally

This is how to authorize a TSO user to use a new logon proc.

Logon as user HERC01 which is authorized to use the ACCOUNT command.

Allocate the UADS file using -

ALLOC F(SYSUADS) DA('SYS1.UADS') SHR

Enter the ACCOUNT command -

ACCOUNT

List the userid to display its current logon proc -

L (HERC03)

This will produce a display something like -

??? HERC03?? USER ATTRIBUTES:? NOOPER? NOACCT??? JCL? NOMOUNT??

???????????? INSTALLATION ATTRIBUTES, IN HEX: 0000?????????????

???????????? MAXSIZE: NOLIM????????????????????????????????????

???????????? USER PROFILE TABLE:???????????????????????????????

???????????? 00000000000000000000000000000000 HERC03???????????

???????????? DESTINATION? =? CENTRAL SITE DEFAULT??????????????

???????????? NO PERFORMANCE GROUPS?????????????????????????????

????? (*)??????????????????????????????????????????????????????

??????? (*)????????????????????????????????????????????????????

????????? TSOLOGON? PROCSIZE=? 8192K, UNIT NAME= TSO???????????

?IKJ56590I LISTED??????????????????????????????????????????????

??????????????????????????????????????????????????????????????? ???????????????????????????????????????????????

Then using the TSO ACCOUNT command, you need to change the PROC name for the user as follows:

C?? (HERC03 * * TSOLOGON)? DATA(ISPLOGON) /* note the highlighted old procname must match the highlighted procname for the user.

END

On 16/01/2021 21:16, Charles Bailey wrote:

I am running tk4-.? It appears that the default TSO logon proc is TSOLOGON and when a user logs on the JCL in SYS1.PROCLIB(TSOLOGON) is executed.

I recently installed Wally's ISPF.? I copied ISP.V2R1M0.INSTALL(ISPLOGON)? to SYS1.PROCLIB and customized a few dataset names.? Now, when I try to logon with this new logon proc I get the following messages:
Logon ===> HERC03 PROC(ISPLOGON)

?ENTER CURRENT PASSWORD FOR HERC03-

?PROCEDURE NAME ISPLOGON NOT AUTHORIZED
?REENTER -

and the only way I can proceed is to enter TSOLOGON as the procedure name.

How can I tell TSO that the procedure ISPLOGON is also authorized?

Assuming you followed the installation instructions to the letter did you make changes to all for TK4 ?

IF not and you don't know ask the TK4 author.

I am running tk4-. It appears that the default TSO logon proc is TSOLOGON and when a user logs on the JCL in SYS1.PROCLIB(TSOLOGON) is executed.

I recently installed Wally's ISPF. I copied ISP.V2R1M0.INSTALL(ISPLOGON) to SYS1.PROCLIB and customized a few dataset names. Now, when I try to logon with this new logon proc I get the following messages:
Logon ===> HERC03 PROC(ISPLOGON)

ENTER CURRENT PASSWORD FOR HERC03-

PROCEDURE NAME ISPLOGON NOT AUTHORIZED
REENTER -

and the only way I can proceed is to enter TSOLOGON as the procedure name.

How can I tell TSO that the procedure ISPLOGON is also authorized?

Thanks,
Charles Bailey

The track number in MVS 3.8 is 16 bit signed. Patched for TK4- for
unsigned. IBM had to fix it for when 3390-2s came out later.

--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

On 1/12/21 2:54 PM, Mike Schwab wrote:

POs are 16 extents, 1 volume. 1 volume limited to 32K tracks TK3
(3390-1.9) or 64K tracks TK4- (3390-3.8)
PS are 16 extents 4GB.

That's 16 extents per volume.? Default (for example, on tape) is six volumes; you can raise the limit.

Most older types (3380 and older?) are smaller than 4 GB.? Where does that limit come, and is per volume or per dataset?

VSAM 4GB over 12x extents 59 volumes.

On Tue, Jan 12, 2021 at 4:20 PM Mark Waterbury
<mark.s.waterbury@...> wrote:

Does anyone recall the maximum size of files (PS, PO, DA, and VSAM) that can be created in MVS 3.8J?

Also, considering that 3380 and 3390 support have apparently been "retrofitted" to the TK4- version ...

Thanks in advance.

--
Drew Derbyshire

WNTC radio - Why Not Try Clyde?

POs are 16 extents, 1 volume. 1 volume limited to 32K tracks TK3
(3390-1.9) or 64K tracks TK4- (3390-3.8)
PS are 16 extents 4GB.
VSAM 4GB over 12x extents 59 volumes.

On Tue, Jan 12, 2021 at 4:20 PM Mark Waterbury
<mark.s.waterbury@...> wrote:

Does anyone recall the maximum size of files (PS, PO, DA, and VSAM) that can be created in MVS 3.8J?

Also, considering that 3380 and 3390 support have apparently been "retrofitted" to the TK4- version ...

Thanks in advance.

--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

Does anyone recall the maximum size of files (PS, PO, DA, and VSAM) that can be created in MVS 3.8J?

Also, considering that 3380 and 3390 support have apparently been "retrofitted" to the TK4- version ...

Thanks in advance.

Hi Rupert,

The next step is installing the latest version of RPF () , REVIEW, IMON and QUEUE (all in )

Cheers,
Rob

There are some sites, you just have to get the URL or IP address and
port number. Moshix had a Turnkey 4 and a z/OS zPDT system, but not
sure if he is giving out IDs any more.

--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

On 10/01/2021 20:16, Bernard Rich wrote:

url for online TK4- ?
Hi. I would like to know more about the online TK4- system, particularly the url and subscription requirements if any.
Thanks,
Bernard

The Turnkey (4) system is based on turnkey 3 but with a lot more added which is it self to be a mainframe operating system called MVS (version 3.8J). It is supplied with all? the supporting software required to reasonably run a working system.

Installing turnkey 4 will take under 10 minutes on Linux or Windows and it is totally self contained.

If you are NOT a knowledgeable mainframe user it will take some time to get your head around the IBM mainframe environment as compared to Windows or Linux - it is totally different with different terminology.

A good thing, if you like many of us are in lock down with plenty of time on your hands.


The good thing is it is free.

Vince

On Tue, Jan 5, 2021 at 1:42 PM Juergen <winkelmann@... <mailto:winkelmann@...>> wrote:

Hi Vince

I'm assuming you are talking about my online TK4- system? There
are four public users: USER01, USER02, USER03, USER04 with
passwords PASS0[1-4].

On Sun, 10 Jan 2021, Giuseppe Vitillaro wrote:

On Sat, 9 Jan 2021, Vince Coen wrote:

Some one gave me this and it works :
x3270 -noverifycert Y:wotho4.ethz.ch:3270

It is equivalent to set:

?x3270.verifyHostCert: false

in your .x3270pro profile, same effect, beside
being "global".

By the way, side note.

I definitely doubt one of us, using x3270 under
Linux to connect to vintage systems running under
hercules, for our beloved hobby, will ever meet
an SSL 3270 host with a certificate signed
from a certification authority.

So, disabling certificate verification,
going back to x3270 3.5 version, may be
a good idea, once for ever :-)

From the other side it may be a good
idea against a "real system" with a
not "self signed" certificate, for
security reasons, your mileage may
vary, of course.

I may only say I've been a user
of a real IBM Z/OS host, running
on real iron.

No SSL at all :-)

When security, certificate verification,
become a must, using "-verifycert" from
command line, with verification disabled
globally at profile level, may be a reasonable
alternative.

Peppe.