Re: Windows build with VS2019 [Was: Newbie question about REVIEW/RPF etc]

#1734

On Sun, Nov 22, 2020 at 4:08 PM Fish Fish <david.b.trout@...> wrote:

Bill Lewis wrote:

[...]
VS2019 seems to change to be updated quite often and seems
to change its mind about things a lot.  It has become a very
aggravating moving target.I've noticed that very phenomenon with Visual Studio for the past several versions now. I'm personally of the mind to NOT use the "latest and greatest" version, and to instead always use the immediately *previous* version (e.g. VS2017 in this case).
Recently?  I noticed that with all the incompatible versions of
Internet Explorer that didn't follow the internet specifications,
Windows where the shortcuts change with every version, Office versions
with different instructions.

<deleted>

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

mail: fish@...

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

Re: mounting a SCRTCH volume

#1733

Hello Rahim,

?

ISPCLT1 is the DDNAME of a (temporary) work dataset for ISPF defined in the ISPFPROC logon procedure. Apparently, MVS has trouble allocating it. I can't say for sure but I suspect MVS wants to allocate it on a DASD with a STORAGE use attribute, and your system does not have enough room left on these DASDs (or the only DASD of that kind if it is the system I think).? Can you still logon, edit and submit jobs? If so I would suggest that you initialize your scratch DASD with ICKDSF, then add it to the VATLST00 member with the STORAGE use attribute (0) and finally re-IPL. People here with deeper knowledge may provide a better solution (and correct my diagnosis if I am wrong on some aspects).

?

Good luck,

?

Rene FERLAND, Montreal?

Re: Windows build with VS2019 [Was: Newbie question about REVIEW/RPF etc]

Bill Lewis

#1732

On Sun, Nov 22, 2020 at 05:16 PM, Fish Fish wrote:

Bill Lewis wrote:

[...]

MAKEFILE.BAT RETAIL MAKEFILE.MSVC 8 -title "WRL Test Build" -a

And it worked. Hercules got built, and what it built works.
FYI: I would personally have used "retail-x64" and not just plain "retail". A plain "retail" builds a 32-bit version of Hercules, whereas "retail-x64" build a native 64-bit version of Hercules, which runs much more efficiently on 64-bit Windows systems (which is what almost all systems are these days; 32-bit systems are becoming more and more rare as time goes by. Virtually *all* systems made these days are 64-bit.)

Just wanted to pass that on: you should use "RETAIL-X64", not plain "RETAIL".

(enter "makefile.bat /?" for more info)

OK, RETAIL-X64 also "just works".

Re: Windows build with VS2019 [Was: Newbie question about REVIEW/RPF etc]

#1731

Bill Lewis wrote:

[...]
   MAKEFILE.BAT RETAIL MAKEFILE.MSVC 8 -title "WRL Test Build" -a

And it worked.  Hercules got built, and what it built works.FYI: I would personally have used "retail-x64" and not just plain "retail". A plain "retail" builds a 32-bit version of Hercules, whereas "retail-x64" build a native 64-bit version of Hercules, which runs much more efficiently on 64-bit Windows systems (which is what almost all systems are these days; 32-bit systems are becoming more and more rare as time goes by. Virtually *all* systems made these days are 64-bit.)

Just wanted to pass that on: you should use "RETAIL-X64", not plain "RETAIL".

(enter "makefile.bat /?" for more info)

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

mail: fish@...

Re: Windows build with VS2019 [Was: Newbie question about REVIEW/RPF etc]

#1730

Bill Lewis wrote:

[...]
VS2019 seems to change to be updated quite often and seems
to change its mind about things a lot.  It has become a very
aggravating moving target.I've noticed that very phenomenon with Visual Studio for the past several versions now. I'm personally of the mind to NOT use the "latest and greatest" version, and to instead always use the immediately *previous* version (e.g. VS2017 in this case).

Today (22 Oct 2020) I created a fresh Windows 10 20H2 under
VMware, and installed VS2019 16.8.2.

I selected workload "Desktop Development with C++", and under
Individual Components, selected "C++ Windows XP Support for
VS 2017 (v141) tools (Deprecated)"Sounds good so far.

After installation, I used Start / Settings / System / About /
/ Advanced System Settings / Environment Variables and created:

   INCLUDE=C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Include

I then rebooted.Again, good so far.

Open from Start menu, VS2019 x64 Native Tools Command Prompt.I personally prefer to build Hercules from the Visual Studio GUI rather than from the command line, but each their own. Whatever floats your boat. <shrug>

In that command prompt window, I changed to SDL-Hercules git
clone directory, and ran:

   MAKEFILE.BAT RETAIL MAKEFILE.MSVC 8 -title "WRL Test Build" -a

And it worked.  Hercules got built, and what it built works.Fantastic! That's good news! Thank you for sharing that, Bill.

To get it to build inside Visual Studio itself, there was more
tweaking needed.Hmmm... So building within Visual Studio is where the problem lies. Build fine from command prompt, but not from Visual Studio? Dang! That's disappointing. :(

In  C:\Program Files (x86)\Microsoft Visual Studio\2019\
\Community\MSBuild\Microsoft\VC\v160 is a file called
Microsoft.Cpp.Common.props.

In that file I found this line:

   <UserRootDir Condition="'$(UserRootDir)' == ''">
   $(LocalAppData)\Microsoft\MSBuild\v4.0</UserRootDir>(Editor's note: above 2 lines are ACTUALLY just *ONE* line.

On this test system that expands to:

   C:\Users\bill\AppData\Local\Microsoft\MSBuild\v4.0

Which didn't exist.  So I created the directory.  It also required
"Show Hidden Files" option to work in there.

(Note, that is the directory that VS2017 used, and that does not
match MSFT published info related to property sheets in VS2019
that I found some months ago)Yes, they keep changing things from one "release" to the next.

PLEASE NOTE that I said "release" and not "version"! With each new version, they release a "preliminary draft" so to speak, and then keep releasing new "drafts" over and over and over again, until eventually they decide they're done, and then release the OFFICIAL *final* version. That is to say, in my experience, all so-called "current" versions that they release are actually ALL just "preliminary-still-under-development-don't-trust-anything-this-release-does-because-it-can-change-drastically-in-a-heartbeat" releases and NOT "official" releases/versions.

That's why I personally recommend NOT using the so-called "current" version and to instead stick with the immediately previous/prior version instead. At least we know IT'S behavior is not going to suddenly change!

Then I copied my old Microsoft.Cpp.x64.user.props (from another
working system with VS2017).Which they've been saying VStudio *will* honor -- if it finds it.

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" ToolsVersion="4.0"
xmlns=">
  <PropertyGroup>

<IncludePath>$(VC_IncludePath);$(WindowsSDK_IncludePath);$(INCLUDE);</Incl
udePath>
  </PropertyGroup>
</Project>

Building under VS2019 GUI then worked.Because it found (and used!) the old VS2017 props! (which we KNOW works!)

I did not attempt a Debug build or to debug anything.

Is it time to start drinking yet?  <sigh>Long past time.  :(

Thanks for the report Bill. Much appreciated.

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

mail: fish@...

Re: mounting a SCRTCH volume

#1729

That sounds very reasonable, and I tried it.

????? :?????????????????????????????????????????????????????????????????????????????? ?
????? 10.00.47 TSU00023? IEF878I END OF IEF877E FOR IBMUSER ISPFPROC ISPFPROC ISPCLT1 ?
??? | 10.00.47 TSU00023 *05 IEF238D IBMUSER - REPLY DEVICE NAME OR 'CANCEL'.????????? ?
??? - 10.01.03?????????? r 5,a95????????????????????????????????????????????????????? ?
????? 10.01.03 TSU00023? IEE600I REPLY TO 05 IS;A95?????????????????????????????????? ?
??? - 10.01.03 TSU00023? IEF490I IBMUSER - INVALID REPLY.???????????????????????????? ?
??? | 10.01.03 TSU00023 *06 IEF238D IBMUSER - REPLY DEVICE NAME OR 'CANCEL'.????????? ?
? 00- 10.02.04?????????? r 6,A95????????????????????????????????????????????????????? ?
????? 10.02.04 TSU00023? IEE600I REPLY TO 06 IS;A95?????????????????????????????????? ?
??? - 10.02.04 TSU00023? IEF490I IBMUSER - INVALID REPLY.???????????????????????????? ?
???? *10.02.04 TSU00023 *07 IEF238D IBMUSER - REPLY DEVICE NAME OR 'CANCEL'.?????????? 



regards;

Rahim 
 

?? 

On Sunday, November 22, 2020, 12:22:19 PM CST, Kevin Monceaux <kevin@...> wrote:

Rahim,

Show quoted text

On Sun, Nov 22, 2020 at 06:16:32PM +0000, Rahim Azizarab via groups.io wrote:

> On Hercules I have at least one completely empty volume;? but I have not
> figured out how to tell MVS that it is a SCRATCH volume.
>
> 0A95????? 3390????? dasd/SY2PKB.cckd??

MVS has figured out how you can tell it:

04.49.33 TSU00023 *05 IEF238D IBMUSER - REPLY DEVICE NAME OR 'CANCEL'.

R 05,A95

--

Kevin

Bruceville, TX

What's the definition of a legacy system? One that works!
Errare humanum est, ignoscere caninum.

Re: mounting a SCRTCH volume

#1728

Rahim,

You might find 
a useful aide memoire.

Chris
-- 
 <cjar1950@...>

----------------------------------------------------------------------------------------------------------------------------------
On Sun, 22 Nov 2020 12:22:09 -0600
"Kevin Monceaux" <Kevin@...> wrote:
Rahim,

On Sun, Nov 22, 2020 at 06:16:32PM +0000, Rahim Azizarab via groups.io wrote:

On Hercules I have at least one completely empty volume;? but I have not
figured out how to tell MVS that it is a SCRATCH volume. 

0A95????? 3390????? dasd/SY2PKB.cckd?? MVS has figured out how you can tell it:

04.49.33 TSU00023 *05 IEF238D IBMUSER - REPLY DEVICE NAME OR 'CANCEL'.

R 05,A95

-- 

Kevin

Bruceville, TX

What's the definition of a legacy system? One that works!
Errare humanum est, ignoscere caninum.

Re: Windows build with VS2019 [Was: Newbie question about REVIEW/RPF etc]

Bill Lewis

#1727

On Fri, Nov 20, 2020 at 10:01 PM, Jeffrey Melton wrote in part:

BTW - A few weeks ago I'd sent you an email regarding your Windows build instructions for SDL Hyperion and have yet to get a response. The Property Sheet modifications as documented in your instructions cannot be done for a clean install of Visual Studio 2019, as those property sheets don't exist? Are there alternate instructions for ensuring that the 'win32.mak' is included for VS2019?

Thanks!? ? BTW - I do like your HercGUI and HercPRT tools and will be in touch with you about purchasing them.?

Jeffrey and Fish,

(in what follows, please excuse my ignorance of how to format messages in Groups.IO)

VS2019 seems to change to be updated quite often and seems to change its mind
about things a lot.? It has become a very aggravating moving target.

Today (22 Oct 2020) I created a fresh Windows 10 20H2 under VMware, and installed VS2019 16.8.2.

I selected workload "Desktop Development with C++", and under Individual Components, selected
"C++ Windows XP Support for VS 2017 (v141) tools (Deprecated)"

After installation, I used Start / Settings / System / About / Advanced System Settings / Environment Variables
and created:

?? INCLUDE=C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Include

I then rebooted.

Open from Start menu, VS2019 x64 Native Tools Command Prompt.

In that command prompt window, I changed to SDL-Hercules git clone directory, and ran:
?? MAKEFILE.BAT RETAIL MAKEFILE.MSVC 8 -title "WRL Test Build" -a

And it worked.? Hercules got built, and what it built works.

---

To get it to build inside Visual Studio itself, there was more tweaking needed.

In? C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160
is a file called Microsoft.Cpp.Common.props.

In that file I found this line:
?? <UserRootDir Condition="'$(UserRootDir)' == '' ">$(LocalAppData)\Microsoft\MSBuild\v4.0</UserRootDir>

On this test system that expands to:
?? C:\Users\bill\AppData\Local\Microsoft\MSBuild\v4.0

Which didn't exist.? So I created the directory.? It also required Show Hidden Files option to work in there.

(Note, that is the directory that VS2017 used, and that does not match MSFT published info related to
property sheets in VS2019 that I found some months ago)

Then I copied my old Microsoft.Cpp.x64.user.props (from another working system with VS2017).

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
? <PropertyGroup>
??? <IncludePath>$(VC_IncludePath);$(WindowsSDK_IncludePath);$(INCLUDE);</IncludePath>
? </PropertyGroup>
</Project>

Building under VS2019 GUI then worked .

I did not attempt a Debug build or to debug anything.

Is it time to start drinking yet?? <sigh>
Bill

Re: mounting a SCRTCH volume

#1726

Rahim,

On Sun, Nov 22, 2020 at 06:16:32PM +0000, Rahim Azizarab via groups.io wrote:

On Hercules I have at least one completely empty volume;? but I have not
figured out how to tell MVS that it is a SCRATCH volume. 

0A95????? 3390????? dasd/SY2PKB.cckd?? MVS has figured out how you can tell it:

04.49.33 TSU00023 *05 IEF238D IBMUSER - REPLY DEVICE NAME OR 'CANCEL'.

R 05,A95

-- 

Kevin

Bruceville, TX

What's the definition of a legacy system? One that works!
Errare humanum est, ignoscere caninum.

Re: mounting a SCRTCH volume

#1725

On Hercules I have at least one completely empty volume;? but I have not figured out how to tell MVS that it is a SCRATCH volume. 

0A95????? 3390????? dasd/SY2PKB.cckd?? 

regards;

Rahim 
? 

??

On Sunday, November 22, 2020, 11:44:00 AM CST, Rene BRANDT via groups.io <rbr146@...> wrote:

Hi Rahim,

How are these units on hercules side ?

0120-015F 0301-0318

搁别苍é

Re: mounting a SCRTCH volume

#1724

Hi Rahim,

How are these units on hercules side ?
0120-015F 0301-0318

搁别苍é

mounting a SCRTCH volume

#1723

Does anyone know how to get rid of 
this error?? I tried all my tricks and it still persists. How can I 
specify a scratch volume?? I have one mounted but it does not see it.



?04.49.31 TSU00023? $HASP373 IBMUSER? STARTED???????????????????????????????????????????? ?
?04.49.31 TSU00023? IEF125I IBMUSER - LOGGED ON - TIME=04.49.31?????????????????????????? ?
?04.49.32 TSU00023? IEF244I IBMUSER ISPFPROC ISPFPROC - UNABLE TO ALLOCATE 4 UNIT(S)????? ?
???????? AT LEAST 4 OFFLINE UNIT(S) NEEDED.?????????????????????????????????????????????? ?
?04.49.32 TSU00023? IEF877E IBMUSER NEEDS 1 UNIT(S)????????????????????? C??????????????? ?
?FOR ISPFPROC ISPFPROC ISPCLT1??????????????????????????????????????????????????????????? ?
?FOR VOLUME SCRTCH-?? 1?????????????????????????????????????????????????????????????????? ?
?OFFLINE, NOT ACCESSIBLE????????????????????????????????????????????????????????????????? ?
?0120-015F 0301-0318 0A99-0AEF??????????????????????????????????????????????????????????? ?
?:??????????????????????????????????????????????????????????????????????????????????????? ?
?04.49.33 TSU00023? IEF878I END OF IEF877E FOR IBMUSER ISPFPROC ISPFPROC ISPCLT1????????? ?
?04.49.33 TSU00023 *05 IEF238D IBMUSER - REPLY DEVICE NAME OR 'CANCEL'.?????????????????? ?
?04.51.03 TSU00023 *IEF882E IBMUSER ISPFPROC ISPFPROC IS WAITING FOR A REPLY TO IEF238D??? 







regards;

Rahim 

?? 

Re: Help request: COBOL Compile, Link and Go

#1722

On Sat, 21 Nov 2020 15:13:58 +1100, "Greg Price" <procegrog@...>
wrote:

On 2020-11-21 6:57 AM, Tim via groups.io wrote:
in FORTRAN the card punch is unit 7Ah yes - that sounds familiar - thanks Tim!

I wouldn't have a clue about the paper tape readerI was thinking it might be 2 if there is such a convention - memories 
are hazy...  If my hazy memory do not fail me, those "standard" units were defined
during compiler generation/configuration.   I don't know when it
happened, perhaps during sysgen?   Anyway, it was somewhat common to
have the unity 2 (FT02F001) as SYSIN and unity 3 (FT03F001) as SYSOUT.
I worked in a place where those were de defined "standard", I don't
recall the pnch unity.

  Without doubt the most common were units 5, 6 and 7, as described
earlier.

I think all of those low numbers initially had a conventional
assignment.

I think VS FORTRAN has or had a customisable upper unit number limit.
Applications would crash off if they tried to use a unit number
higher than was configured.? We just used to make it 99, IIRC.

Cheers,
Greg

  Roxo

--
---------------- Non luctari, ludare -------------------+ WYSIWYG
Fernando M. Roxo da Motta <mvs@...>                | Editor?
Except where explicitly stated I speak on my own behalf.|  VI !!
                PU5RXO                                  | I see text,
------------ Quis custodiet ipsos custodes?-------------+ I get text!

Re: [Marketing Mail] Re: [Marketing Mail] Re: [H390-MVS] Newbie question about REVIEW/RPF etc

#1721

开云体育

Jeff,

Not Greg, but maybe I can help? the “SCROLL AMT” (top right corner) is the amount to scroll – CS is for Cursor – PG is for PAGE – or you can enter a number of lines – if you like to scroll up or down 5 lines at a time *when you use UP or DOWN (PF7 or PF8) – enter ?5

?

I happen to like CS – I position my cursor – hit the appropriate key (PF7 or PF8) – and it will scroll the line the cursor is on to the top of the screen

And when the cursor is on the top – acts like PG – so a full page

?

-J-

?

Show quoted text

From: [email protected] <[email protected]> On Behalf Of Jeffrey Melton via groups.io
Sent: Friday, November 20, 2020 11:17 PM
To: [email protected]
Subject: [Marketing Mail] Re: [Marketing Mail] Re: [H390-MVS] Newbie question about REVIEW/RPF etc

?

Greg,

Thanks so much for your response!!? I love using RFE (even though you said it does the wrong thing above - it still works wonderfully on any extended display settings I throw at it from any of the terminal emulators I have!).? Though I'm still a "newbie" at RFE, I'm getting better and better, and would be happy to offer not only my newbie status but my writing skills to use in developing an "RFE for Beginners" training manual.?

I got my feet wet using RFE with the Moshix videos.? My own experience in actual mainframe world was early in my career as IMS and NOMAD2 application programmer in VM/CMS and MVS in the days of XA.? So I know enough of the general vocab and basics, a good bit about tools we don't have on Hercules/MVS3.8j, but not a whole lot about system programming, and definitely not at your own technical depth.

I do have one, nagging question for you, however, about RFE that I haven't yet found the answer to - and I'll be sure to put it in any manual I may help to develop....? What are the valid values for the "Scroll ===>" prompt and their meanings?? All I see is the default "CS" but there are many references in the help text to say that the 'scroll' value is used if no operand is specified.? I've tried putting in other values in there and it seems to just overwrite them with 'CS'.

Re: [Marketing Mail] Re: [Marketing Mail] Re: [H390-MVS] Newbie question about REVIEW/RPF etc

#1720

Jeffrey Melton wrote:

[...]
BTW - A few weeks ago I'd sent you an email regarding
your Windows build instructions for SDL Hyperion and
have yet to get a response. The Property Sheet modifications
as documented in your instructions cannot be done for
a clean install of Visual Studio 2019, as those property
sheets don't exist  Are there alternate instructions
for ensuring that the 'win32.mak' is included for VS2019?Sorry about that. I've been so incredibly busy concentrating on Hercules that I've for the most part been ignoring anything distracting me from that effort -- especially things that would likely take more than a trivial amount of time and effort to resolve (such as VS2019). MY only suggestion at this point would be to not use VS2019 at all, and to use VS2017 instead.


BTW - I do like your HercGUI and HercPRT tools and will
be in touch with you about purchasing them.Thanks. Every sale helps.

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

mail: fish@...

Re: Trying to add a printer or punch as sockdev

#1719

开云体育

I've just (backed up and...) altered 'SYS1.JES2PARM' for another printer for class Y, which

is already defined as held output. I'll have a play with HercPrt now :-)

Thank you.

Roops

On 20/11/2020 19:30, Joe Monk wrote:

Show quoted text

"I don't know how JES2 links PRT1 to an MVS device address!"

Thats in member JES2PM00 in SYS1.PARMLIB....

*?

* ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?LOCAL PRINTERS ? ? ? ? ? ? ? ? ? ? ? ? *?

*?

PRINTER1 ? ? ? UNIT=00E,CLASS=A,FCB=6,FORMS=STD1,SEP,AUTO ? ? ? ? ? ? ?C

? ? ? ? ? ? ? ?NOPAUSE,START ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 1403 ? ? ??

PRINTER2 ? ? ? UNIT=00F,CLASS=M,FCB=6,FORMS=STD1,SEP,AUTO ? ? ? ? ? ? ?C

? ? ? ? ? ? ? ?NOPAUSE,UCS=TB,START ? ? ? ? ? ? ? ? ? ? ? ? ?3211 ? ? ??

*?

Joe

On Fri, Nov 20, 2020 at 12:15 PM Rupert Reynolds <rupertreynolds@...> wrote:

Thanks. That JES2 command has moved things forward--I can connect now.

But I realise I need to RTFM on JES2 and printing. I didn't ever have much to do with printing, and it was JES3 in my shop.

I don't know how JES2 links PRT1 to an MVS device address!

Roops.

On Fri., Nov. 20, 2020, 17:01 Rahim Azizarab via , <rahimazizarab=[email protected]> wrote:

You already have the definition?

B 0003 3211 PRT? sockdev print fcbck IO[4]

I usually use 1403 for Printer;? I am not sure if the highlighted part is necessary. Just go to your Web browser and type localhost:4444;? you may need to do a $S PRT1 on your SCP (Hercules) console too.? ?

Rahim?
? ?

??

On Friday, November 20, 2020, 10:49:49 AM CST, Rupert Reynolds <rupertreynolds@...> wrote:

Can anyone suggest what to do next, please? I'm trying to understand the various options for TCP/IP links

between MVS and the host. I'm mostly ignorant of the Herc options for sockdev devices and CTCs etc, and I

did do a SYSGEN a few times many years ago, but most of the details are forgotten.

I don't think it's a configuration problem on the host, as I can connect to

port 3505 (RDR) and submit jobs just fine, although it shows as a 2540 in MVS (00c).

?

Given this result from /D U in the Hercules console, I was assuming that there are two 3211 printers in the IOGEN, 002 and 003.

HHC00008I /d u

15.36.56?????????? IEE450I 15.36.56 UNIT STATUS 447

?UNIT TYPE STATUS? VOLSER VOLSTATE?? UNIT TYPE STATUS? VOLSER VOLSTATE

?002? 3211 A???????????????????????? 003? 3211 OFFLINE

?009? 3215 C???????????????????????? 00C? 2540 A

?00D? 2540 A???????????????????????? 00E? 1403 A

?00F? 1403 A???????????????????????? 010? 3277 OFFLINE

?011? 3277 OFFLINE?????????????????? 01F? 3215 OFFLINE

?070? 2703 OFFLINE?????????????????? 071? 2703 OFFLINE

?072? 2703 OFFLINE?????????????????? 073? 2703 OFFLINE

?074? 2703 OFFLINE?????????????????? 075? 2703 OFFLINE

?076? 2703 OFFLINE?????????????????? 077? 2703 OFFLINE

?080? 2703 OFFLINE?????????????????? 081? 2703 OFFLINE

?082? 2703 OFFLINE?????????????????? 083? 2703 OFFLINE

?084? 2703 OFFLINE?????????????????? 085? 2703 OFFLINE

?086? 2703 OFFLINE?????????????????? 087? 2703 OFFLINE

If I hit Esc to view hardware from Hercules' POV, 003 is missing. So I added 003 in the TK4-.cnf :-

# unit record devices

#

0002 3211 prt/prt002.txt ${TK4CRLF}

0003 3211 sockdev

And now it appears in the Hercules hardware list (below), but I can't connect to it on port 4444 from

Win64 telnet, a simple socket client I bashed together, or using telnet from Linux. For comparison,

I /can/ connect to Hercules port 21 if I start FTPD.

Roops

Enc:-

U Addr Modl Type Assignment

A 0002 3211 PRT? prt/prt002.txt crlf print fcbck IO[2]

B 0003 3211 PRT? sockdev print fcbck IO[4]

C 000E 1403 PRT? prt/prt00e.txt crlf print fcbck IO[21]

D 000C 3505 RDR? 3505 sockdev ascii trunc eof IO[4]

E 000D 3525 PCH? pch/pch00d.txt ascii IO[2]

F 0480 3420 TAPE * IO[4] maxsize=0 eotmargin=128K deonirq=N

G 010C 3505 RDR? jcl/dummy ascii trunc eof IO[2]

H 010D 3525 PCH? pch/pch10d.txt ascii IO[2]

I 000F 1403 PRT? prt/prt00f.txt crlf print fcbck IO[117]

J 030E 1403 PRT? log/hardcopy.log crlf print fcbck IO[449]

K 0009 3215 CON? *syscons cmdpref(/) IO[237]

L 00C0 3270 DSP? * IO[4]

M 00C1 3270 DSP? * IO[4]

N 00C2 3270 DSP? * IO[4]

O 00C3 3270 DSP? * IO[4]

P 00C4 3270 DSP? * IO[4]

Q 00C5 3270 DSP? * IO[4]

R 00C6 3270 DSP? * IO[4]

S 00C7 3287 DSP? * IO[2]

T 03C0 3270 DSP? GROUP=TCAM IO[4]

U 03C1 3270 DSP? GROUP=TCAM IO[4]

V 03C2 3270 DSP? GROUP=TCAM IO[4]

W 03C3 3270 DSP? GROUP=TCAM IO[4]

X 03C4 3270 DSP? GROUP=TCAM IO[4]

Y 03C5 3270 DSP? GROUP=TCAM IO[4]

Z 03C6 3270 DSP? GROUP=TCAM IO[4]

. 03C7 3270 DSP? GROUP=TCAM IO[4]

. 0610 3088 CTCA IO[1]

. 0611 3088 CTCA IO[1]

. 0660 3705 LINE Read count=39, Write count=37 IO[77]

. 0661 3705 LINE Read count=39, Write count=37 IO[77]

. 0662 3705 LINE Read count=39, Write count=37 IO[77]

. 0663 3705 LINE Read count=39, Write count=37 IO[77]

. 0664 3705 LINE Read count=30, Write count=27 IO[58]

. 0665 3705 LINE Read count=30, Write count=27 IO[58]

. 0666 3705 LINE Read count=30, Write count=27 IO[58]

. 0667 3705 LINE Read count=30, Write count=27 IO[58]

Re: Help request: COBOL Compile, Link and Go

#1718

Thanks Chris,

I thought I had copies of pretty much all the Fortran manuals on Bitsavers, but I must have missed that one

Tim

On Saturday, 21 November 2020, 9:38:04 pm AEDT, cjar1950 via groups.io <cjar1950@...> wrote:

Tim,

If you look at pp 65-69 of http://www.bitsavers.org/pdf/ibm/360/fortran/SC28-6852-1_OS_FORTRAN_H_Pgmr_Jun72.pdf,
you will see the published definitions for Fortran H.

.
.

Chris

--
<cjar1950@...>

----------------------------------------------------------------------------------------------------------------------------------

Show quoted text

On Sat, 21 Nov 2020 04:13:30 -0600
"Joe Monk" <joemonk64@...> wrote:
> "Did the S360 have a paper tape reader? I had never heard of one, but then
> I was an applications programmer/analyst - never a systems programmer, and
> I never knew much about mainframe hardware"
>
> Yep. The model 2671 paper tape reader along with the 2822 controller.
>
> Joe
>
> On Fri, Nov 20, 2020 at 11:53 PM Tim via groups.io <aardvarkguard-hercules=
> [email protected]> wrote:
>
> >
> >
> > On Saturday, 21 November 2020, 3:14:06 pm AEDT, Greg Price <
> > procegrog@...> wrote:
> >
> >
> > On 2020-11-21 6:57 AM, Tim via groups.io wrote:
> > >> in FORTRAN the card punch is unit 7
> > >Ah yes - that sounds familiar - thanks Tim!
> >
> > >>
> > >> I wouldn't have a clue about the paper tape reader
> > >I was thinking it might be 2 if there is such a convention - memories
> > >are hazy...
> >
> > >I think all of those low numbers initially had a conventional assignment.
> >
> > Did the S360 have a paper tape reader? I had never heard of one, but then
> > I was an applications programmer/analyst - never a systems programmer, and
> > I never knew much about mainframe hardware
> >
> >
> > >I think VS FORTRAN has or had a customisable upper unit number limit.
> > >Applications would crash off if they tried to use a unit number higher
> > >than was configured.? We just used to make it 99, IIRC.
> >
> > Yes VS Fortran did have a customisable upper unit number. I found that out
> > when the systems guys put in a new version of VS Fortran, and one of our
> > programs promptly aborted with an invalid unit number message, or something
> > like that. I just looked at some of my old JCL members (which I copied to a
> > CD before the mainframe was decommissioned where I used to work) and in one
> > of the FORTRAN ones I made a comment that you needed to specify UNTABLE=99
> > in the VSFORTL macro (not that I really know what that means..).
> >
> > Ever since that occasion, the first thing I did when they put in a new
> > version of VS Fortran was to run a small test program that used unit number
> > 80! (I can't remember why I didn't use 99 - perhaps 80 was the highest unit
> > number we used).
> >
> > >Cheers,
> > >Greg
> >
> > Tim
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>

Re: Help request: COBOL Compile, Link and Go

#1717

Tim,

If you look at pp 65-69 of ,
you will see the published definitions for Fortran H.

.
. 
 
Chris

-- 
 <cjar1950@...>



----------------------------------------------------------------------------------------------------------------------------------
On Sat, 21 Nov 2020 04:13:30 -0600
"Joe Monk" <joemonk64@...> wrote:
"Did the S360 have a paper tape reader? I had never heard of one, but then
I was an applications programmer/analyst - never a systems programmer, and
I never knew much about mainframe hardware"

Yep. The model 2671 paper tape reader along with the 2822 controller.

Joe

On Fri, Nov 20, 2020 at 11:53 PM Tim via groups.io <aardvarkguard-hercules=
[email protected]> wrote:



On Saturday, 21 November 2020, 3:14:06 pm AEDT, Greg Price <
procegrog@...> wrote:


On 2020-11-21 6:57 AM, Tim via groups.io wrote:
in FORTRAN the card punch is unit 7Ah yes - that sounds familiar - thanks Tim!
I wouldn't have a clue about the paper tape readerI was thinking it might be 2 if there is such a convention - memories
are hazy...I think all of those low numbers initially had a conventional assignment.Did the S360 have a paper tape reader? I had never heard of one, but then
I was an applications programmer/analyst - never a systems programmer, and
I never knew much about mainframe hardware


I think VS FORTRAN has or had a customisable upper unit number limit.
Applications would crash off if they tried to use a unit number higher
than was configured.  We just used to make it 99, IIRC.Yes VS Fortran did have a customisable upper unit number. I found that out
when the systems guys put in a new version of VS Fortran, and one of our
programs promptly aborted with an invalid unit number message, or something
like that. I just looked at some of my old JCL members (which I copied to a
CD before the mainframe was decommissioned where I used to work) and in one
of the FORTRAN ones I made a comment that you needed to specify UNTABLE=99
in the VSFORTL macro (not that I really know what that means..).

Ever since that occasion, the first thing I did when they put in a new
version of VS Fortran was to run a small test program that used unit number
80! (I can't remember why I didn't use 99 - perhaps 80 was the highest unit
number we used).

Cheers,
GregTim

Re: Help request: COBOL Compile, Link and Go

#1716

"Did the S360 have a paper tape reader? I had never heard of one, but then I was an applications programmer/analyst - never a systems programmer, and I never knew much about mainframe hardware"

Yep. The model 2671 paper tape reader along with the 2822 controller.

Joe

Show quoted text

On Fri, Nov 20, 2020 at 11:53 PM Tim via <aardvarkguard-hercules=[email protected]> wrote:

On Saturday, 21 November 2020, 3:14:06 pm AEDT, Greg Price <procegrog@...> wrote:

On 2020-11-21 6:57 AM, Tim via wrote:
>> in FORTRAN the card punch is unit 7
>Ah yes - that sounds familiar - thanks Tim!

>>
>> I wouldn't have a clue about the paper tape reader
>I was thinking it might be 2 if there is such a convention - memories
>are hazy...

>I think all of those low numbers initially had a conventional assignment.

Did the S360 have a paper tape reader? I had never heard of one, but then I was an applications programmer/analyst - never a systems programmer, and I never knew much about mainframe hardware

>I think VS FORTRAN has or had a customisable upper unit number limit.?
>Applications would crash off if they tried to use a unit number higher
>than was configured.? We just used to make it 99, IIRC.

Yes VS Fortran did have a customisable upper unit number. I found that out when the systems guys put in a new version of VS Fortran, and one of our programs promptly aborted with an invalid unit number message, or something like that. I just looked at some of my old JCL members (which I copied to a CD before the mainframe was decommissioned where I used to work) and in one of the FORTRAN ones I made a comment that you needed to specify UNTABLE=99 in the VSFORTL macro (not that I really know what that means..).

Ever since that occasion, the first thing I did when they put in a new version of VS Fortran was to run a small test program that used unit number 80! (I can't remember why I didn't use 99 - perhaps 80 was the highest unit number we used).

>Cheers,
>Greg

Tim

Re: Help request: COBOL Compile, Link and Go

#1715

On Saturday, 21 November 2020, 3:14:06 pm AEDT, Greg Price <procegrog@...> wrote:

On 2020-11-21 6:57 AM, Tim via groups.io wrote:
>> in FORTRAN the card punch is unit 7
>Ah yes - that sounds familiar - thanks Tim!

>>
>> I wouldn't have a clue about the paper tape reader
>I was thinking it might be 2 if there is such a convention - memories
>are hazy...

>I think all of those low numbers initially had a conventional assignment.

Did the S360 have a paper tape reader? I had never heard of one, but then I was an applications programmer/analyst - never a systems programmer, and I never knew much about mainframe hardware

>I think VS FORTRAN has or had a customisable upper unit number limit.?
>Applications would crash off if they tried to use a unit number higher

>than was configured.? We just used to make it 99, IIRC.

Yes VS Fortran did have a customisable upper unit number. I found that out when the systems guys put in a new version of VS Fortran, and one of our programs promptly aborted with an invalid unit number message, or something like that. I just looked at some of my old JCL members (which I copied to a CD before the mainframe was decommissioned where I used to work) and in one of the FORTRAN ones I made a comment that you needed to specify UNTABLE=99 in the VSFORTL macro (not that I really know what that means..).

Ever since that occasion, the first thing I did when they put in a new version of VS Fortran was to run a small test program that used unit number 80! (I can't remember why I didn't use 99 - perhaps 80 was the highest unit number we used).

>Cheers,

>Greg

Tim