Sorry, I misspoke.? I took out and IPLed my SP5 image today and found that I'm using a VTAM CTC link to talk to VM/ESA and RSCS talks through VTAM.? I reconfigured RSCS on each end to use the CTC directly and got the same results you reported.? I'd swear I had this working at one point but, if so, I don't know how and I don't have the configuration information available to get it working anymore.

Sorry for the noise.

Jeff

If you want to try again, I have a VM/ESA to VM/SP5 CTCE connection in my network.? My SP5 is not HPO, but hopefully it's close enough.? We could compare configs and see what might be different.? Your LINKDEFINEs seem a little simplistic from what I recall (mine have PARMs on them that you don't mention).

Jeff

... with VM/SP items ...

Hi Dutch,

As the author of the CTCE code, I can confirm that RSCS connections between a VM/SP and VM/ESA using a CTCE link should work. The ATTNDELAY parameter on the VM/SP side was added some years ago in order to circumvent a problem which we believed to be a possible VM/SP bug. Unfortunately I don't recall some of the details, and in addition i'm not all that familiar with VM/CP items (like I never touched any DMKRIO's). Perhaps some other people may be able to help with what I suspect to be an RSCS node name setup problem.

I whish you good luck !?

Cheers,

Peter

P.S.: Is "Dutch" really your name ? It matches my (birth) nationality ...? ?

All,

?

Thanks for the help.? I'm dropping this project and looking at another direction for providing a server on HNET.

?

Dutch

It's VM/SP 5 HPO.? It does support NJE over 3088s according to the docs. and it "almost" works which it wouldn't if there was no hardware support.? It would abort on the START.

?

VM/ESA doesn't support 2703 so a BSC line won't work.? That's why I'm going to the CTC method.

?

I'm coming to believe it's the CTCE connection that's failing.? ?I installed another VM/SP in place of the VM/ESA and the two do exactly the same thing - eliminating the issue of incompatibility between ESA and SP.

?

Next step is to connect to ESA systems together over the CTCE.? If that works, it's VM/SP having issues with the CTCE.? If? it doesn't the CTCE is buggy or misconfigured.

开云体育

What version of VM/SP? ? Maybe you could try a BISYNC line and 2703 emulation? ?I’m very fuzzy on when 3088s were first supported by RSCS.

Playing around with the VM370CE. Got the APL that Bob Bolch put together.?

The terminal has an APL option there.

I'm using the OEC emulator () and it does work well emulating a 3174.?

What I would REALLY like to do is get this working with APL.?? Has anybody had any luck doing that???

Thanks!

-Karl

I could use a little help or advice from those more experienced with VM and RSCS than I am.? I'm almost there, but right at the end, things won't connect.

?

Any advice would be greatly appreciated!

?

The goal is to link RSCS on VM/ESA to RSCS on VM/SP using a CTCE link.? ?The VM/ESA system is named HELENA and the VM/SP is DIANA.

Both sides are using Windows 7 with the latest prebuilt SDL Hercules 4.6.??

The "hardware" seems configured properly and the two sides' CTCE links connect up properly with "Incoming accepted" messages in the Hercules console window.

HELENA's RSCS CONFIG has this LINKDEF:?LINKDEFINE DIANA TYPE NJE LINE 500 NODE DIANA
DIANA's RSCS CONFIG has this LINKDEF:?LINKDEFINE HELENA TYPE NJE LINE 500 NODE HELENA

The SYSTEM NETID is setup on both systems and have the correct LOCAL name in their RSCS configs.? Both have DEDICATE 500 in their directories.?
VM/ESA autosenses the 3088 and the SP DMKRIO is configured properly so far as I can tell.

?

The Problem:

When I START HELENA on DIANA it goes 'active' and waits.? Then when I START DIANA on HELENA I get a "Line 500 dataset ready" message on DIANA's console and both sides remain 'active' but will not 'connect'.

If on the other hand I START DIANA on HELENA it goes 'active' and waits.? Then I START HELENA on DIANA and I get an "Invalid NJE sIgnon card" message on HELENA's console and the link DIANA de-activities.

(I did put the ATTNDELAY parameter on the CTCE Hercules entries on the VM/SP side - if I don't I get I/O errors.? I use 100 for the delay number.)

?

Baffled!

?

Thanks

Dutch

?

?

Thank you all!

Now everything falls into place!

Best regards.

Alejandro,

It is easy enough to add a new volume for the purpose of user minidisk space.? Here are the basic steps.? There are of course other variations or considerations depending on what else you might do with the volume such as adding TEMP space or TDSK space, but for now we’ll just focus on adding space for minidisks since that is what you asked.

If I were adding a new volume for minidisks right now, I would do this below.? I’m providing this summary at a high level; for actual command syntax you can look it up and research/learn:

1.?????? Create a new volume in Hercules using DASDINIT.? Use whatever options you like for your needs, device type, whether it is compressed or not, volume name.? You should specify that the volume has alternate cylinders? (-a).

2.?????? Attach the new disk to Hercules with the Hercules attach command, or place the new disk in the Hercules configuration before you start Hercules.? The device address you select must be one that is already defined to VM (in DMKRIO) and of the right device type; there are lots of extra available.

3.?????? Bring up your VM system and log on to MAINT.

4.?????? Vary online the new volume at the device address you selected, e.g., CP VARY ONLINE cuu

5.?????? Issue CP ATTACH to attach the new volume to MAINT? (e.g.,? CP ATTACH cuu to MAINT).

6.?????? From MAINT, Spool your punch to MAINT, e.g.? CP SPOOL PUN TO MAINT

7.?????? Make sure MAINT’s virtual reader queue is empty.

8.?????? Then punch a copy of the iplable format/allocate program, e.g.,? PUN IPL FMT S (NOH

9.?????? Then issue IPL 00C to start the format/allocate program.

10.?? Select F for Format.? Be careful to ensure you enter the correct device address!? Fill out the prompts for device address, desired volume name and device type.? I’d recommend formatting the entire volume, so for a 3350 that would be cylinder 000 to 555.? You don’t strictly have to do this but it is good policy; you never know what other areas might be put on the volume later.? At the bare minimum though format cylinder 0.

11.?? After formatting is completed, select A for Allocate.? Answer the prompts carefully about device address, type, and volume name.? Then you will get a prompt about entering allocation data, (e.g., TYPE CYL CYL).? For your purposes, you just want PERM space.? So type in this (for a 3350):?

PERM 000 555

12.?? Then type END and press enter.

13.?? That concludes the allocation and format.? You can now #CP IPL CMS

14.?? You don’t need to add the volume to any SYSUSR macro in DMKSYS or anything like that as long as there is only PERM space allocated.? Just make sure the disk volume is defined in your Hercules configuration and the volume will come up online and ready to use with each IPL.

15.?? When you want to add user minidisks, just add them to the system directory, starting at Cylinder 1 for how many cylinders you need.? Each new minidisk is added after that, ensuring there are no cylinder specification errors where you might overlap one minidisk into another on the same volume.? Later VM versions had a tool (DISKMAP) to help prevent errors but I am not sure what is available on VM/CE as I write this.

16.?? Once you finish adding one or more minidisks and/or users, issue the DIRECT command to make the directory changes take effect.

17.?? Then you can logon to the userid that is getting a new minidisk and use the CMS FORMAT command to format the minidisk for CMS use.

It looks like a lot of steps but for an experienced VM person this is about 5-10 minutes work.

Regards,
Bob

开云体育

Hi all.

I'm dealing with user management, and the first thing I want to do is to create a regular user... So far, I see quite straightforward to add a directory entry based on CMSUSER, linking CMS System and Help minidisks, but the interesting part of this is to provisioning, at least, a MDISK? entry to have an A unit where PROFILE EXEC would sat (as I read around on the books)

Creating a new 3350 is an easy shot, and I'm aware there's an unused 3350 provided by default to create minidisks as required... however, this is the part of I'm starting to get confused as I read documentation:

- By one side of my reads, I get to the conclussion that, just by having a 3350 'seen' by the hypervisor (dasdinit, edit herc conf, and there you go!), it is possible to just start defining MDISK statements on users (carefully avoiding cylinder everlapping), and then let them use the FORMAT command to format and label them... and that's it!
- However, on another side, I read about the existence of the IPL utils on the System (S) disk, being IPL FMT of particular interest here... here another path of action appears to be possible, with format and allocate applications present for the purpose of well... allocating and formating disks. Further doubts arise as I fail to distinguish between certain such as PERM or TDSK formats.

I'm probably confused/biased by my experience, where, block-device partitioning and file-system initializtion/formatting are clearly recognizeable/distinct steps, however I feel I'm missing something here, I have not a clear picture on what is the right way to go.

Do we have to somehow 'partition' DASDs (by means of allocate/format) prior to use them as MDISKs? or is Allocate/Partition only needed for CP/System only related stuff (spooling , etc) and 'user-space' storage is obtained by just accesing disk cylinders directly?

Thank you very much in advance.
Regards.

Thanks!

So far I have a cisco 7200, I've ordered a 4port serial card, a serial cable, and an old ISA IBM sdlc card.? So far all I have is the serial cable.? But I think this ought to be enough to try to replicate the 9track's setup.

It'll be interesting to see if it actually works, or is there something much more larger going on ...?

Thanks

On 5/31/23 03:12, neozeed wrote:

I've been trying to dig around in the dark and the best I can figure is that almost everything online is in AWS format, but SIMH needs its TAP format.

take a look at vtapeutils



I found this, might have some insight as well.



I highly recommend rather than taking any version from download, especially from a Linux distro, get and build your own version (Linux is pretty simple with latest versions) from source for your machine.

I'm not a super expert but a problem I'd had with DASD forever has gone away with the latest.? I couldn't get anyone to look at it in my local circle, as they'd been away too long to want to jump start brain cells, but 6 months ago, I decided to give it my "every so often" try and built a version 4.5 which had no problem as I was having, and am now running what I wanted.

Anyway, I think vtapeutil might do what you like for your TAP, AWS issues.? searching for anything on AWS tapes is horrible, since Amazon now pollutes that search.

I'm certainly interested in anything you find with the actual hardware to hercules experiments.
thanks
Jim

Thanks!? Long time no see through the portals of time!

I've been having this strange need to do some networking and after years of looking at a dlsw article, i've been trying to recreate it.



This has gotten me interested again, and I almost think I had some partial success.? Other than it not working.

I'd written about my adventure here:



But what had brought me to VM/370 is that I've seen SIMH has a 360 emulator, and I've been curious to see what it'd take to get it running.



In the status the following is in there:

• BOS/360:? ?Works.
• TSS/370:? ?Works.
• VM/370:? ? Works.

So obviously this interested me greatly as well!

I've been trying to dig around in the dark and the best I can figure is that almost everything online is in AWS format, but SIMH needs its TAP format.

There is a BOS image on bitsavers:



I'll have to try that first, see if I can reproduce anything.

In the meantime I do have a cisco 7200 (they are so cheap now!), and I've ordered a 4 port serial card, a serial cable with db25 end, and an IBM SDLC card, to see if I can get a PC to talk directly to Hercules with this setup.

Gregg Levine wrote:

[...]

Then others took many turns to create releases that closely
approximate what is now Z/VM, that Z stands for I believe
Zero Wait States.

I always thought the "z" in z/VM and z/OS, etc. stood for "z/Architecture", IBM's 64-bit architecture (formerly known as ESAME" Enterprise Systems Architecture Modal Extensions), but apparently it actually stands for "zero downtime":

*

"The zSeries, zEnterprise, System z and IBM Z families
were named for their availability – z stands for
zero downtime."


*

"IBM zSystems is a family name that's used by IBM for all
of its z/Architecture mainframe computers, beginning with
the z900 released in 2000 to the IBM z16 released in May
2022. (The "z" stands for "zero downtime," which reflects
the reliability of the system.)"

Or perhaps it does not,

Not. :)

--
"Fish" (David B. Trout)
Software Development Laboratories

mail: fish@...

Hello!
I realized when I saw a familiar email address pop up in my mail here
that confirmed that we have a new member. Welcome to that lucky
individual. You will find that we are all friendly people in this
list. Nearly all questions regarding the groupings of VM are allowed
here, VM is indeed Virtual Machine, and it's a product of IBM that
goes back a very long time. To that extent those of us who do, run a
variety of VM that is VM/370 Release 6, and a very capable fellow
released to us several items. They are found in many places. Then
others took many turns to create releases that closely approximate
what is now Z/VM, that Z stands for I believe Zero Wait States. Or
perhaps it does not, it does go well with their families of System Z
machines.

Please feel free to ask your many questions.
-----
Gregg C Levine gregg.drwho8@...
"This signature fought the Time Wars, time and again."