开云体育

Here is some information that I added to my site several years ago for COBOL that applies to the MVT era COBOL: http://www.jaymoseley.com/hercules/compiling/how_to.htm#topic11 There is also a pdf that

Marco, Our Cobol is lacking in any documentation. I suggest you look at page 62-3 in

Thank you Chris I did notice that the examples were referencing CONSOLE, but I did not imagine that that would make a difference between SYSOUT and SYSPRINT. Would you have any pointer to manuals that

Marco, In TK4-, look in SYS2.JCLLIB, at TESTCOB, and PRIMCOB1 etc Chris. -- <cjar1950@...>

Marco, Hopefully to add to what others have advised: If you DISPLAY "TEST". then you need a GO.SYSOUT DD SYSOUT=* If you have 0065 SPECIAL-NAMES. 0066 CONSOLE IS CNSL and DISPLAY "TEST" UPON CNSL.

Thanks. That did it.? The ``` //GO.SYSOUT DD SYSOUT=* ``` is what was missing. Somehow I could not find any example mentioning it.? I should have thought about it. All the best Marco -- Marco

You need to add? ??GO.SYSOUT DD SYSOUT=* regards; Rahim

The COBOL DISPLAY statement outputs to the file defined by the SYSOUT DD card. JJ

"If in doubt, give it what it wants" :-) In this case, it wants a //SYSOUT DD statement. I nothing of COBOL, but how about //SYSOUT DD SYSOUT=* Roops

Hi apologies for the probably stupid newbie question.? I get an error while trying to execute the attached job, which is a pretty standard (AFAIU) COBOL Hello World job. The problem appears to be an

When running TSO on a non-SNA terminal, does it use SNA/VTAM at all? Can one use TSO in this configuration with VTAM not running? Just curious Khalid

Gentles, I am with Patrik on this. This is about helping people to run MVS on whatever platform they chose, be it Linux, Windows, MacOS, Solaris, OpenVMS or whatever OS. How do you know the user isn't

Frankly, Rahim, this is a pretty silly statement, even for you. Some people like pork, some people dont. Some people eat cows, some people dont. Without Microsoft, DOS, and Windows, the PC world would

Hello Rahim, Am 18.11.2020 um 18:13 schrieb Rahim Azizarab via groups.io <rahimazizarab@...>: Besides your post being largely off topic in here… Most people are using Windows for a

Emancipate yourself by switching to Linux.? You can move forward much quicker with Linux mint than with Windows.? Windows is for the corporate folks that have a lot of money to burn and time to

I think ATTN button functionality depends on having an SNA session. If your TSO terminal is an MVS 3270 I/O device with its own device address, then that is a non-SNA session and so ATTN does not

Oh, I can stop it! If PA1 doesn't work, /C U=ROOPS at the console gets the job done :-) Sometimes, PA1 interrupts (which is not my experience from MVS/XA and TSO/E in the 1990s). But I'm wondering

<jb.reginato@...> wrote: It is very common to have the TSO prompt right after the first PA1. At the prompt an "END" command should finish the execution. HTH

Try PA1 twice De: [email protected] <mailto:[email protected]> <[email protected] <mailto:[email protected]> > Em nome de Rupert Reynolds Enviada em: quarta-feira, 18 de novembro de 2020 07:08

Try PA1 De: [email protected] <[email protected]> Em nome de Rupert Reynolds Enviada em: quarta-feira, 18 de novembro de 2020 07:08 Para: [email protected] Assunto: [H390-MVS] Attn does not