Re: Optimization, CPU time, and related issues

On 2/18/2014 1:59 PM, John Gilmore wrote: ... The cache and other such programmer-inaccessible machinery are devices for optimizing and in particular speeding up the code that programmers write or translators generate. Their characteristics, mostly but not entirely undocumented, must be inferred

Re: Xmitting file between disconnected systems

>>I would TRS PACK the XMIT file, FTP it to target, then TRS UNPACK the >>file, and receive. >> >Why? Because of the size of the XMTI file? Apart from that it doesn't help much since also the tersed file needs to be copied to the target system where it must be received into an FB1024 dataset. I

Re: Optimization, CPU time, and related issues

Ed Jaffe opines: >Of course, "Fugget about it" is expected from IBM, but there are >software vendors making a comfortable living helping their customers >save serious cash by minimizing their monthly peak R4HAs. Some of them >spread out batch workload; some of them raise, lower, and move LPAR caps

Re: Optimization, CPU time, and related issues

To amplify a part of what you said @Tim Sipples a goodly part of MY case load is in support of my Software Group VP Ray Jones in helping z/OS customers manage their usage and hence part of their software bill. Others in IBM have complementary roles. And some of you here have definitely been par

Re: Optimization, CPU time, and related issues

Most of what Timothy Sipples says is fair controversial comment on Edward Jaffe's post. His use of the verb 'opines' is not. As far back as the Alexandrian rhetoricians money collected for my worthy cause has gone into a 'war chest' and that collected to advance your despicable ends has instead g

Re: Performance question - adding

Obviously if the loop was that tiny that would be a solution. But the loop is larger and cannot spare a register. On Tue, 18 Feb 2014 07:18:06 -0600 Mike Schwab wrote: :>Then optimize with :>L Rx,SUM or XR Rx,Rx :>loop :> A Rx,CURRENT :>endloop :>ST Rx,SUM. :> :>On Tue, Feb 18, 2014 at 2:31 AM

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

Greg, Yes, there are 3 volumes in that pool - mod 9. There are about 21,000 cylinders available. On Tue, 2/18/14, Greg Shirey wrote: Subject: Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80 To: IBM-MAIN@LISTSERV.UA.E

Re: Branch (was: Performance question - adding)

On Tue, Feb 18, 2014 at 5:20 PM, Shmuel Metz (Seymour J.) < shmuel+ibm-m...@patriot.net> wrote: > In > , > on 02/18/2014 >at 08:02 AM, Peter Relson said: > > >So it's probably less about optimizing existing code (unless it's in > >a loop) than about understanding what is best for your new cod

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

I re-ran the DEFINE again because the output was purged. Below is the SYSIN and the error message : DEFINE CLUSTER ( - NAME(CICSALL.APPLIC.PROD.ZWA6) - DATACLAS(CICSALL) - STORCLAS(CICSALL) -

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

Tom, I checked the STORCLASS ROUTINE and it doesn't. Below are excerpts of the ACS routine: FILTLIST CICSALL INCLUDE(CICSALL.**) WHEN (&DSN EQ &CICSALL) DO SET &STORCLAS = 'CICSALL' EXIT CODE(0) END

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

Lizette, I tested all the ACS rules before I moved it to Prod. I can allocate dsns via ISPF 3.2 if I do not specify the VOLSER. I only encounter problems when I code the volsers. On Tue, 2/18/14, Lizette Koehler wrote: Subject: Re: IDC3009I ** V

Re: Optimization, CPU time, and related issues

On Wed, 19 Feb 2014 05:40:10 -0500, John Gilmore wrote: >Marketing people, those of both IBM and >its competitors, do of course try to put the best possible face on the >characteristics of their products; and it would be naif to expect them >to behave differently. tis a pity some of them choose t

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

I think Tom is onto something. Seems like there is something in your ACS routines that if you code VOLSER, then it "doesn't" do the rest. Check the ACS routines again for what occurs with VOLSER, or by chance are there certain privileges granted when your ID does thing? I know in ours there

Measurement of performance at the opcode Level, was: Optimization, CPU time, and related issues

John Gilmore wrote: Locality of reference was always a good notion, and now it is a crucially important one. I would like to ask some additional questions in this context: How precise are the measures provided by TIMEUSED? Do these measures take into account the delays caused by cache misses? A

Re: assembler

In , on 02/18/2014 at 09:52 PM, John Gilmore said: >Gerhard: >You have caricatured/radically misrepresented what I wrote in a >fashion that I regard as offensive, disreputable, and unseriös. PKB. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

Lizette, Here is the DATACLAS Construct : Command ===> CDS Name . . . : SYS2.SMS.SCDS Data Class Name : C

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

I checked to see if there is the GUARANTEED SPACE for this DSN and my user however there is none. On Wed, 2/19/14, Jousma, David wrote: Subject: Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80 To: IBM-MAIN@LISTSERV.UA.ED

Re: assembler

Since virtual storage is now so much less expensive and so much more available than storage [1] was 50 years ago, why not be really extravagant and use one whole byte per store?  If the byte contains 0, then the store number is not valid, or something like that, and if the byte contains anything

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

This is a sample of our code to allow "special people" or certain overrides to be honored by SMS. Do you have any checking for VOLSER? Like when a VOLSER is specified to quit doing SMS assignments? /*/ /* ALLOW SPECIAL USERS

Re: assembler

On Tue, Feb 18, 2014 at 10:02 PM, Robert A. Rosenberg wrote: > At 17:42 -0500 on 02/18/2014, Gerhard Postpischil wrote about Re: > assembler: > > > You seem to be deliberately confounding the issue. There is no efficient >> way of testing the validity of a bit number using only bytes. Let me >> s

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

David, I'll take a second look. When I checked earlier I didn't notice anything. Thanks. On Wed, 2/19/14, Jousma, David wrote: Subject: Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80 To: IBM-MAIN@LISTSERV.UA.EDU Rec

Re: assembler

John McKown wrote: >So why not a "test bit" instruction, instead of needing to generate a "bit >mask" from the "bit number", then do something like an EX of an NI or some >such (as I'm sure many have seen and done). This could be a simple RX format >instruction. The register would contain the b

Re: assembler

On 2/18/2014 10:30 PM, Shmuel Metz (Seymour J.) wrote: at 09:52 PM, John Gilmore said: Gerhard: You have caricatured/radically misrepresented what I wrote in a fashion that I regard as offensive, disreputable, and unseriös. PKB. I'm still waiting on his repeated promise to stop post

Re: Xmitting file between disconnected systems

I am going to throw my 2cents worth in here. Since you are already using XMIT and RECEIVE and the 3270 emulator file transfer, let's stick with them and not make anything more confusing, because, YES, you can do all those fancy things like TERSE and FTP, but those are not always an option and s

Re: assembler

On 2/19/2014 8:20 AM, John McKown wrote: Going a bit OT on this, but this talk about bits - the testing and setting thereof, makes me curious about why IBM doesn't simplify it a "bit" (pun intended). I think we have way to many instructions already I have a subroutine to maintain a bit table,

Re: Measurement of performance at the opcode Level, was: Optimization, CPU time, and related issues

Arthur, In my experience the TIMEUSED macro is useful chiefly for timing the CP usage of entire routines, which may of course be short ones, not individual instructions. Care is required in using it. The two successive TIMEUSED macros employed to obtain a difference/measurement should be so pla

Re: assembler

John, When I worked VSE many moons ago , we build a buffer area between the end of the program and end of the partition, then build a bitmap to reference it. Like the old f.rt I am I didn't save the code..but I like your idea.. Scott ford www.identityforge.com from my IPAD > On Feb 19, 2014

Re: assembler

..want to trade On 2/19/2014 7:49 AM, Elardus Engelbrecht wrote: John McKown wrote: So why not a "test bit" instruction, instead of needing to generate a "bit mask" from the "bit number", then do something like an EX of an NI or some such (as I'm sure many have seen and done). Th

Re: Packed decimal (again!)

Ted MacNEIL wrote: >Careful. In Canada the first four digits identify the issuer. Ooh, do tell - did some Googling but didn't find this. http://en.wikipedia.org/wiki/Social_Insurance_Number talks about the first digit being significant, however. This still proves the point I believe you were ma

Re: Xmitting file between disconnected systems

On 2014-02-19, at 01:22, Hunkeler, Peter wrote: >>> I would TRS PACK the XMIT file, FTP it to target, then TRS UNPACK the >>> file, and receive. >>> >> Why? > > Because of the size of the XMTI file? Apart from that it doesn't help much > since also the tersed file needs to be copied to the targ

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

Willie, It looks good. So my next question is why are you coding a VOLSER when you want SMS to manage it? For SMS Management I rarely code a VOLSER. Or if I do, the users use VOL(*) rather than a specific volser. I agree with the others. Check you ACS code for either USER filtlist or VOLSER o

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

I would also use ISMF TEST function and code the VOLSER and see what happens. I would think your TEST should have issues if you code the VOLSER in the TEST Panel. If it is not stopped in the ISMF TEST function, I would open a case to IBM to find out why. Lizette > -Original Message- >

Re: Xmitting file between disconnected systems

>> Because of the size of the XMTI file? Apart from that it doesn't help much >> since also the tersed file needs to be copied to the target system where it >> must be received into an FB1024 dataset. > >A valid concern, but no help and perhaps a distraction when the >OP was struggling with dat

Re: assembler

On Wed, 19 Feb 2014 12:51:33 +, DASDBILL2 wrote: >Since virtual storage is now so much less expensive and so much more available >than storage [1] was 50 years ago, why not be really extravagant and use one >whole byte per store?  If the byte contains 0, then the store number is not >valid,

Re: assembler

From: "John McKown" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Wednesday, February 19, 2014 7:20:20 AM Subject: Re: assembler   >They have done some, such as with Find LeftMost One and Population Count (could somebody explain to me what this might really be used for?).   One possible use of Popul

Re: assembler

On Wed, Feb 19, 2014 at 8:47 AM, DASDBILL2 wrote: > From: "John McKown" > To: IBM-MAIN@LISTSERV.UA.EDU > Sent: Wednesday, February 19, 2014 7:20:20 AM > Subject: Re: assembler > > >They have done some, such as with Find LeftMost One and > Population Count (could somebody explain to me what this

Re: assembler

John McKown wrote Population Count (could somebody explain to me what this might really be used for?). I find it useful for processing large assembled bit maps. An example is what I call a Marked Days Table. Such an MDT is really a bit map having one bit for each day in some unbroken sequence

Re: assembler

Ah, the never-ending trade-off between cost of developing, debugging, and ongoing maintenance of the code by other non-specialized people (simple vs. elegant code) and the expense at execution time (how many bazillion times per second does the code generate poor locality of reference access patt

Re: Optimization, CPU time, and related issues

On Tue, 18 Feb 2014 18:39:42 -0500, Shmuel Metz (Seymour J.) wrote: > > at 01:47 PM, Tony Harminc said: > >>Indeed this is the way conditional execution and branching works (and >>has always worked) in channel programs. > >No. Every generation believes that it invented sex, ... > ObQoheleth? F

Re: assembler

dasdbi...@comcast.net (DASDBILL2) writes: > Since virtual storage is now so much less expensive and so much more > available than storage [1] was 50 years ago, why not be > really extravagant and use one whole byte per store? If the byte > contains 0, then the store number is not valid, or somethin

Re: assembler

You're right.  I had forgotten about the S/360 model 67.  Most of the 360s in production were not model 67s, however.  Certainly all the 360s which I knew anything about were non-virtual 360s.  The first virtual storage-capable processor I ever saw and touched was in 1974 running SVS. So what w

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

Does that snippet of STORCLAS code actually execute? Could some earlier code in the routine bypass it (e.g., if a volser is specified, set &STORCLAS to null and exit)? :>: -Original Message- :>: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :>: Behalf Of willie

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

Doesn't this convince you that your ACS routines do something different when a volser is specified? It seems your ACS routines need further analysis. :>: -Original Message- :>: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :>: Behalf Of willie bunter :>: Sent: W

Re: assembler

On 19 February 2014 11:12, DASDBILL2 wrote: > So what was the correct term for non-virtual storage way back then for non-67 > models of the S/360? Storage? Real storage? V=R storage? The terms I > heard most frequently included the word "core." In my circles the term "core" survived for qui

Re: assembler

On 2/19/2014 9:29 AM, Tony Harminc wrote: In my circles the term "core" survived for quite a long time after the introduction of the first 370 models with non magnetic-core storage (the 158 and 168, followed closely by the lower end 138, 148 and so on). And amusingly the UNIX people still use "co

Re: assembler

t...@harminc.net (Tony Harminc) writes: > In my circles the term "core" survived for quite a long time after the > introduction of the first 370 models with non magnetic-core storage > (the 158 and 168, followed closely by the lower end 138, 148 and so > on). And amusingly the UNIX people still use

Re: Optimization, CPU time, and related issues

This chart has helped me: http://xkcd.com/1205/ Regards, Greg Shirey -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: assembler

On Wed, 19 Feb 2014 12:29:42 -0500, Tony Harminc wrote: >In my circles the term "core" survived for quite a long time after the >introduction of the first 370 models with non magnetic-core storage Third-party semiconductor memory was available for 360 models by the mid 1970s. At the university (

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

This is exactly why every EXIT statement in my routines are matched with a WRITE statement : SELECT (&STORCLAS) . . . WHEN ('SCCICS') DO SET &STORGRP = 'SGCICS' WRITE 'SGSC070 ' &DSN ' ' &STORCLAS ' ' &STORGRP EXIT END . The string "SGSC070" identifies 1 and only 1 Exit. I

Enforcing subparameters in a MVS command

Hi everyone, I would like to know if there is a way to enforce subparameters that are not originally mandatory in a MVS command. I know I could probably use a Console package like AutoOperator to do that, but I don’t intend to be tied up to an ISV product because of it. Are there any exit that

Re: Enforcing subparameters in a MVS command

> -Original Message- > From: IBM Mainframe Discussion List On Behalf Of ITURIEL DO NASCIMENTO NETO > > Hi everyone, > > I would like to know if there is a way to enforce subparameters that are not > originally mandatory in a > MVS command. > I know I could probably use a Console package

Re: assembler

>From a modern perspective the single-level store in FS would've meant at least 128-bit addressing, perhaps 256, by now. And there'd be consequences to that. :-) Cheers, Martin Martin Packer, zChampion, Principal Systems Investigator, Worldwide Banking Center of Excellence, IBM +44-7802-245-58

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

Unless you are working with the guaranteed space attributes under SMS, you should not (or need to) specify VOLUMEif you are targeting SMS storage. VOLUME vs STORCLAS/MGMTCLAS should be view as mutually exclusive. I also use writes in my ACS routines so that I know exactly which path the allocat

RES: Enforcing subparameters in a MVS command

John, Great. Thanks. Atenciosamente / Regards / Saludos Ituriel do Nascimento Neto BANCO BRADESCO S.A. 4250 / DPCD Engenharia de Software Sistemas Operacionais Mainframes Tel: +55 11 3684-2177 R: 42177 3-1402 Fax: +55 11 3684-4427 Agora é BRA. BRA de Brasil. BRA de Bradesco. Patrocinador of

Re: assembler

On Wed, Feb 19, 2014 at 1:24 PM, Martin Packer wrote: > From a modern perspective the single-level store in FS would've meant at > least 128-bit addressing, perhaps 256, by now. And there'd be consequences > to that. :-) > > Cheers, Martin > > Martin Packer, > > Look at the current "System i". It

Re: Optimization, CPU time, and related issues

On 18 February 2014 18:39, Shmuel Metz (Seymour J.) wrote: > on 02/18/2014 at 01:47 PM, Tony Harminc said: > >>Indeed this is the way conditional execution and branching works (and >>has always worked) in channel programs. > > No. "No" what? > Every generation believes that it invented sex, I

Re: assembler

On Wed, 19 Feb 2014 19:24:06 +, Martin Packer wrote: >From a modern perspective the single-level store in FS would've meant at >least 128-bit addressing, perhaps 256, by now. And there'd be consequences >to that. :-) I'll grant you that there might be some shops that will have to deal with 16

Re: assembler

On Feb 19, 2014, at 2:30 PM, Tom Marchant wrote: > I'll grant you that there might be some shops that will have to deal with 16 > million terabytes before too long. That is what 64 bits will address. Is > anyone there yet? It will be a long time before 128 bits is not enough. I think one of th

Doc needed - Distribution Control System - IOMOD module

Greetings, We are trying to assist customer who wishes to run binary, "as is" printer ready data out to printers using the IOMOD program of Distribution Control System. As is usual in these cases customer has no doc available.. Anyone out there know where we can get some information on IOMOD - a

Re: Optimization, CPU time, and related issues

I have one work task. Use to do it about twice a week, because that was all the typing I could stand. So I wrote an Access DB to hold the info, and a script to read the files from the various servers that needed to be checked. Now I can double click on all the servers in 5 hours every day, and d

Re: assembler

john.archie.mck...@gmail.com (John McKown) writes: > Look at the current "System i". It really looks a lot like what has been > discussed here. It has, theoretically, a 128 bit virtual addresses. > Everything is an object. It has the single level storage so there aren't > really any "disk files" as

Re: assembler

Curtis G Pew wrote: I think one of the folks involved in Solaris zfs (not to be confused with OMVS zFS) calculated that the entropy generated by a full 128-bit address space would result in enough heat to boil all the oceans on earth. So I believe 128 bits is enough for a long time. and I am pu

Re: assembler

On Feb 19, 2014, at 4:29 PM, John Gilmore wrote: > and I am puzzled. Is this entropy the entropy of thermodynamics or > information theory? The quantity having the dimensions J/K, Joules > per Kelvin? > > In what sense is entropy ever 'generated'? > > Or is this perhaps a technically loose fi

Re: assembler

On Wed, 19 Feb 2014 17:29:17 -0500, John Gilmore wrote: >Curtis G Pew wrote: > > >I think one of the folks involved in Solaris zfs (not to be confused >with OMVS zFS) calculated that the entropy generated by a full 128-bit >address space would result in enough heat to boil all the oceans on >earth

BSAM POINT on TAPE files

Can anyone tell me how the BSAM POINT macro works for tape. Is there a device command that will just skip say 1000 blocks with only one device end returned and with no data transfer over the channel (what I really hope happens)? Or does it just READ 1000 blocks without placing them in memory? The

Re: assembler

Does it? 'Population' presumably means full physical realization. As I have already pointed out, this has not been achieved even for 64-bit addresses. Moreover, it is not likely to be achieved for them anytime soon, but AMODE(64) does anyway have its uses. The notional equations = | are sp

Re: BSAM POINT on TAPE files

You should look here: Data Management Macro Instructions z/OS V1R10.0-V1R11.0 DFSMS Introduction SC26-7397-03 On Thu, Feb 20, 2014 at 9:56 AM, David Speake wrote: > Can anyone tell me how the BSAM POINT macro works for tape. > Is there a device command that will just skip say 1000 blocks with

Re: IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80

Caveat: I get the daily digest so responses are in the Pioneer 10 grouping... Willie: as mentioned by others, all SMS information must be generated by the ACS routines since you have specified none. It would appear that an 'extended' DataClas *is* being assigned otherwise you'd get a differen

Re: BSAM POINT on TAPE files

Duh, The Introduction manual was not totally helpful, however it forced (pointed) me back into SC26-7408-08 DFSMS Macro Instructions for Data Sets where I had been also unsuccessfully. Double Duh The format of the CNTRL macro is: [label] CNTRL dcb address {,SS,{1|2}} {,SP,{1|2|3}} {,SK,{

Re: assembler

john.archie.mck...@gmail.com (John McKown) writes: > Look at the current "System i". It really looks a lot like what has been > discussed here. It has, theoretically, a 128 bit virtual addresses. > Everything is an object. It has the single level storage so there aren't > really any "disk files" as

Re: Optimization, CPU time, and related issues

re: http://www.garlic.com/~lynn/2014c.html#62 Optimization, CPU time, and related issues aka the internal operation of the machine ... and the execution elements actually being managed ... are becoming less & less directly related to the external instruction architecture. for instance, risk arch

Re: assembler

dasdbi...@comcast.net (DASDBILL2) writes: > Since virtual storage is now so much less expensive and so much more > available than storage [1] was 50 years ago, why not be > really extravagant and use one whole byte per store?  If the byte > contains 0, then the store number is not valid, or somethi

Re: assembler

t...@harminc.net (Tony Harminc) writes: > In my circles the term "core" survived for quite a long time after the > introduction of the first 370 models with non magnetic-core storage > (the 158 and 168, followed closely by the lower end 138, 148 and so > on). And amusingly the UNIX people still use

Re: Optimization, CPU time, and related issues

re: http://www.garlic.com/~lynn/2014c.html#62 Optimization, CPU time, and related issues aka the internal operation of the machine ... and the execution elements actually being managed ... are becoming less & less directly related to the external instruction architecture. for instance, risk arch

Rewriting Assembler to COBOL was Re: Branch (was: Performance question - adding)

On 19 Feb 2014 03:48:24 -0800, in bit.listserv.ibm-main you wrote: >On Tue, Feb 18, 2014 at 5:20 PM, Shmuel Metz (Seymour J.) < >shmuel+ibm-m...@patriot.net> wrote: > >> In >> , >> on 02/18/2014 >>at 08:02 AM, Peter Relson said: >> >> >So it's probably less about optimizing existing code (unl

Re: Optimization, CPU time, and related issues

On 19/02/2014 4:00 PM, Ed Jaffe wrote: On 2/18/2014 1:59 PM, John Gilmore wrote: ... The cache and other such programmer-inaccessible machinery are devices for optimizing and in particular speeding up the code that programmers write or translators generate. Their characteristics, mostly but not

Hercules

Hello all: I am trying to install the fully free version of Hercules. Any help would be appreciated! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: IN

Re: Hercules

Which OS? Windows (which version)? Linux (which distro)? Other? Have u gone to http://www.hercules-390.org ? On Feb 19, 2014 9:38 PM, "Cameron Seay" wrote: > Hello all: > > I am trying to install the fully free version of Hercules. Any help would > be appreciated! > > --

Re: Hercules

You might want to join the Hercules List Community email addresses: Post message: hercules-...@yahoogroups.com Subscribe:hercules-390-subscr...@yahoogroups.com Unsubscribe: hercules-390-unsubscr...@yahoogroups.com List owner: hercules-390-ow...@yahoogroups.com Files and archives at

Re: BSAM POINT on TAPE files

If you ant an "example" look at CBTTAPE.ORG and look for either DITTO or DEBE and take a look at the source. I know it uses EXCP instead of BSAM but it should give you a flavor. Ed On Feb 19, 2014, at 5:01 PM, Wayne Bickerdike wrote: You should look here: Data Management Macro Instructions

Re: assembler

At 08:41 -0600 on 02/19/2014, Paul Gilmartin wrote about Re: assembler: On Wed, 19 Feb 2014 12:51:33 +, DASDBILL2 wrote: Since virtual storage is now so much less expensive and so much more available than storage [1] was 50 years ago, why not be really extravagant and use one whole byte p

Re: BSAM POINT on TAPE files

David Speake wrote: >Duh, No Duh here! Only wise persons ask questions and you received excellent replies from the all-wise gurus. :-) >SC26-7408-08 DFSMS Macro Instructions for Data Sets where I had been also >unsuccessfully. That manual is a blessing. I used it to fix a defective [nameless