It Runs under ISPF... No ISPF. No TSO is the basic requirement. 

ITschak 


| Itschak Mugzach | Director | SecuriTeam Software |
| Email: [EMAIL PROTECTED] | Mob: +972 522 986404 | Skype: Itschak
Mugzach | Web: www.Securiteam.co.il  | 

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Ian S. Worthington
Sent: Tuesday, July 29, 2008 6:32 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Statistics when writing PDS members

Is there no way of calling LMMSTATS from C++?

i

------ Original Message ------
Received: Tue, 29 Jul 2008 05:21:55 PM BST
From: Itschak Mugzach <[EMAIL PROTECTED]>
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Statistics when writing PDS members

> Kirk,
> 
> I don't know an interface, but you can open the PDS as a sequential 
> file
and
> read the directory until you get ZZ (if I remember correctly). Don't 
> know what will happen if you'll try to write it back..., but I presume 
> that if
it
> conforms to the PDS directory format, it will be OK. 
> 
> Itschak
> 
> 
> | Itschak Mugzach | Director | SecuriTeam Software |
> | Email: [EMAIL PROTECTED] | Mob: +972 522 986404 | Skype: 
> | Itschak
> Mugzach | Web: www.Securiteam.co.il  |
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On 
> Behalf Of Kirk Wolf
> Sent: Tuesday, July 29, 2008 6:14 PM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Statistics when writing PDS members
> 
> I'm working on some code written in C++ (with some assembler) that 
> does I/O to Unix files and z/OS datasets using the C library.
> The C library supports writing PDS members, but it doesn't supporting
adding
> ISPF-style member statistics.
> 
> I'm looking for suggestions on how to create statistics for a member 
> that I add or update.  Of course, I could rewrite all of the PDS I/O 
> in assembler, but I'd rather not.  It would be nice if there were a 
> callable service that would just update the directory and add 
> statistics, with the restriction that my code really can't require a
> TSO TMP or ISPF environment.   Also, I assume that updating a member
> with statistics is expensive since it would probably have to rewrite 
> the whole directory to expand the directory entry length.
> 
> On a related question, I know that it is customary when adding or 
> updating PDS members for code to allocate the dataset with DISP=SHR 
> and then to use the ISPF ENQ protocols for serializing the directory
> and member names.   Our plan is to allow this method, or to allow
> DISP=OLD allocation of the dataset.    My question is this:  which
> technique should be the default?
> 
> Any ideas or suggestions would be appreciated.
> 
> Kirk Wolf
> Dovetailed Technologies
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO 
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
> 
> 
> __________ NOD32 3280 (20080718) Information __________
> 
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO 
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
> 
> 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the
archives at http://bama.ua.edu/archives/ibm-main.html


__________ NOD32 3280 (20080718) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to