Hash File size
Moderators: chulett, rschirm, roy
Hash File size
Hi !
Is there way to know hash file size (include its directories created by DS) from DS DEsigner or Manager or Director or Administartor ?
Is there way to know hash file size (include its directories created by DS) from DS DEsigner or Manager or Director or Administartor ?
Hi,
You might be able to do it via universe commands.
Perhaps by analyze.file command.
It really depends on what implementation you had in mind.
why you need to know the exact file size?
will you use both dynamic and static files or not?
what do you want gain by having this data?
and so on.
so please explain what you want to do.
You might be able to do it via universe commands.
Perhaps by analyze.file command.
It really depends on what implementation you had in mind.
why you need to know the exact file size?
will you use both dynamic and static files or not?
what do you want gain by having this data?
and so on.
so please explain what you want to do.
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
snassimr,
no, none of these tools actually look at the disk size of the physical file, they only know about the logical view of the file and it's contents.
You will need to use your OS and get that information from there.
You do have a UV/Basic function called FILEINFO() which does give you a lot of information about an open file unit, check the BASIC Programmer's Guide for details on how to call it; but it too will only give you indirect sizing information.
no, none of these tools actually look at the disk size of the physical file, they only know about the logical view of the file and it's contents.
You will need to use your OS and get that information from there.
You do have a UV/Basic function called FILEINFO() which does give you a lot of information about an open file unit, check the BASIC Programmer's Guide for details on how to call it; but it too will only give you indirect sizing information.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Execute the following command from Administrator client command window.
This will show the physical size of the DATA.30 and OVER.30 components of the dynamic hashed file. What you are planning to do with this information I have no idea - perhaps setting up an alarm when either reaches 1.5GB?
Code: Select all
DOS /C "dir hashedfilepath"
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Why do you 'need' this?
Rather than tell us what you think you need, you're better off explaining what it is you are trying to accomplish. It goes beyond just asking "Is there way to know hash file size (include its directories created by DS) from DS DEsigner or Manager or Director or Administartor or a routine or something?". Tell us what you need it for, what you are planning on doing with it - the 'why' in the equation. Then the people here can help you work out a way ( usually several ) to accomplish that, and those ways may be totally different than the way you thought you needed to go.
Rather than tell us what you think you need, you're better off explaining what it is you are trying to accomplish. It goes beyond just asking "Is there way to know hash file size (include its directories created by DS) from DS DEsigner or Manager or Director or Administartor or a routine or something?". Tell us what you need it for, what you are planning on doing with it - the 'why' in the equation. Then the people here can help you work out a way ( usually several ) to accomplish that, and those ways may be totally different than the way you thought you needed to go.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
snassimr,
what error does the FILEINFO command give you?
what error does the FILEINFO command give you?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
That's an... interesting... and rather limiting... directive. I'm not even going to ask why that would be a 'requirement'.
What's supposed to happen once they go over the 100MB limit?
ps. The BASIC manual states that SYSCOM line only works with "PI/Open flavor accounts". Try removing it and using the numeric key rather than the nmemonic or 'Symbolic' name when you call FILEINFO.
What's supposed to happen once they go over the 100MB limit?
ps. The BASIC manual states that SYSCOM line only works with "PI/Open flavor accounts". Try removing it and using the numeric key rather than the nmemonic or 'Symbolic' name when you call FILEINFO.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Instead of SYSCOM (which hails from Prime INFORMATION (ancient history)), you need UNIVERSE.INCLUDE. Also, prefer FILEINFO.H to FILEINFO.INS.IBAS (same origin).
Code: Select all
$INCLUDE UNIVERSE.INCLUDE FILEINFO.H
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
UniVerse allows accounts to be created in various different "flavors" to emulate different origin systems more closely. DataStage always creates accounts as IDEAL flavor, therefore you will never have PI/open flavor.
You can force the Routine to compile and run in PI/open flavor using the compiler declaration $OPTIONS PIOPEN but that would be introducing a maintenance nightmare.
PI/open was one of a number of non-PRIMOS implementations of Prime INFORMATION produced by Prime Computer, Inc. In fact, the earliest version was a (licensed) copy of UniVerse!
You can force the Routine to compile and run in PI/open flavor using the compiler declaration $OPTIONS PIOPEN but that would be introducing a maintenance nightmare.
PI/open was one of a number of non-PRIMOS implementations of Prime INFORMATION produced by Prime Computer, Inc. In fact, the earliest version was a (licensed) copy of UniVerse!
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.