/usr/lpp/java/common (was: IBM Knowledge Centre)

On Mon, 11 Jul 2016 08:31:55 +0800, Timothy Sipples wrote: >John McKown wrote: >>Am I being too "reactionary" ...? > >IBM doesn't think so: > >https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.hkcz100/kczos043.htm > >That link is specifically for z/OS 2.2. Refer to

Re: IBM Knowledge Centre

On Sun, Jul 10, 2016 at 7:31 PM, Timothy Sipples wrote: > John McKown wrote: > >Am I being too "reactionary" in wanting to have my documentation > >on the same system as it is documenting? I.e. z/OS documentation > >on z/OS needing only access to z/OS without any other >

Re: IBM Knowledge Centre

John McKown wrote: >Am I being too "reactionary" in wanting to have my documentation >on the same system as it is documenting? I.e. z/OS documentation >on z/OS needing only access to z/OS without any other >"specialized" software on a "desktop"? IBM doesn't think so:

Re: IBM sold TWS (IWS) ???

The following was posted on the 'Watching IBM' Facebook group page on July 6: Sent to Watching IBM: "Hi and thanks for your contributions in sharing information about IBM across countries. Please, as usual keep me anonymous. Today IBM Italia announced to employee of IBM Tivoli Workload

Re: IBM sold TWS (IWS) ???

On 7/10/2016 3:34 AM, Juergen Kehr wrote: there were some rumours upcoming last week, that IBM solds TWS/IWS (Tivoli/IBM Workload Scheduler) to a Chinese company. Is this a (bad) joke or is there any truth behind these rumours? The seemingly never-ending staff reductions at IBM have forced

Re: Error in a simple COBOL program

The SYSIN file in the OP's JCL was the source member for the compile. It has no relation to the program's execution other than the coincidence of the name SYSIN. Very likely, this caused some confusion. Obviously the OP is working on learning COBOL and JCL, and possibly many other things.

Error in a simple COBOL program

Ah. My carefully crafted scheme has failed. The SYSIN is the COBOL program, and I suppose it is "some considerable number of years" since it needed the step-name for that to work. Thanks Walt for pointing that out. OK, run it under TSO. Don't compile-and-go, just compile and link. Assign the

Error in a simple COBOL program

Sure. And there is a dataset with SYSIN data on it, which implies no human intervention. What do we do now, explode due to the contradiction? As I said, my guess is a non-Mainframe training example applied to the Mainframe. For a COBOL program on the Mainframe, I see no point in "interacting"

CBT Tape Version 491 is now on www.cbttape.org

Hi Folks, I'm happy to say that CBT Version 491 is now available on www.cbttape.org. Of course, new Updates will be put on the Updates page from now on. As always, please download from the Updates Page first, if the file number you are looking for is there. In that way, you'll get the

Re: Error in a simple COBOL program

The original program includes the following statements: DISPLAY "TO END PROGRAM, ENTER 0.". DISPLAY "TO CALCULATE SALES TAX, ENTER THE SALES AMOUNT.". The above statements are executed prior to "ACCEPT"ing every inputted amount. If the intent of this program was to

IBM sold TWS (IWS) ???

Technically, and the technical is important because it is a legal thing, Insider Trading is buying or selling based on knowledge that you have from within an organisation which is not yet public. OK, for the letter of the law, there is always a search-engine. Passing on the same inside

Error in a simple COBOL program

Here's one with the priming read, and a little trick for multiple ACCEPTs, because ACCEPT doesn't give "end of file". +1+2+3+4+5+6+7-- ID DIVISION. PROGRAM-ID. CALC1000. DATA DIVISION. FILE SECTION.

Error in a simple COBOL program

On Sunday, 10 July 2016 15:56:12 UTC+2, Eric Mendelson wrote: > From tso allocate Sysin to your terminal and call the load module from tso > Then re-type the test data from the dataset. Thinking further, I have used ACCEPT to obtain a variable number of input cards. Just not tried it

Error in a simple COBOL program

No. If you look at the SYSIN dataset that was used in the original JCL, it is has a DSN on it, a member of a PDS. The entire "session" responses can be included within that dataset without a problem. Or with a problem if the data does not conform to what the COBOL program "expects". It makes no

Re: IBM sold TWS (IWS) ???

If this were public knowledge, I would think there would be news items on IBM website or the Financial companies would be sending out notices of the sale or potential sale. Since I am not seeing anything at this time, possibly false rumor. Or the deal is not completed to the point where it can

Re: HealthChecker rc 0401 in rexx check

Hello Peter, I write the length of the buffer before save to PQE and it is about 900 bytes. This explains why the four or fifth time I save into this area the program get this error. The docs per Rexx are not well documented as some of the services are supplied implicit like the one O used. BTW,

Re: HealthChecker rc 0401 in rexx check

An home grown on. בתאריך 10 ביול 2016 16:10,‏ "Peter Relson" כתב: > >A rexx check runs several iterations and failed with the above diagnostic > >information. It is my understanding that 0401 is the reason code. If so, > it > >refers to implicit call to HZSQUERY that tried to

Re: Error in a simple COBOL program

From tso allocate Sysin to your terminal and call the load module from tso Sent from my iPhone > On Jul 10, 2016, at 9:18 AM, Keith Smith wrote: > > What is missing is a method of making the program "know" that you want it > to get input from your screen. (or so it

Re: Error in a simple COBOL program

What is missing is a method of making the program "know" that you want it to get input from your screen. (or so it seems) If you want terminal input you need to use CICS or ISPF PANEL processing. Or possibly execute this program from TSO. It has been a while but I know of no way to tie a batch

Re: HealthChecker rc 0401 in rexx check

>A rexx check runs several iterations and failed with the above diagnostic >information. It is my understanding that 0401 is the reason code. If so, it >refers to implicit call to HZSQUERY that tried to retieve (or update) the >PQE area (which the rexx uses to pass information. Reason code 0401

IBM sold TWS (IWS) ???

Hello, there were some rumours upcoming last week, that IBM solds TWS/IWS (Tivoli/IBM Workload Scheduler) to a Chinese company. Is this a (bad) joke or is there any truth behind these rumours? Does anybody know more about this message? Kind regards Juergen