Using /tmp directory

Archive of postings to DataStageUsers@Oliver.com. This forum intended only as a reference and cannot be posted to.

Moderators: chulett, rschirm

Locked
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Using /tmp directory

Post by admin »

Hi all,

We are running DataStage 4.0 on Solaris box.
DataStage is using /tmp directory as a default for memory-mapping hashed files, which is defined in dsenv file:

DS_MMAPPATH=/tmp; export DS_MMAPPATH
DS_MMAPSIZE=32; export DS_MMAPSIZE
DS_MAXWRITEHEAPS=1; export DS_MAXWRITEHEAPS

Is it actually a good idea to use /tmp directory? How much space is usually required?

Thank you,
Leonid Frumker
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Post by admin »

I know that if you are writing a hashed file with write cache enabled then this will cause memory map files to be created in the directory specified. I am not sure if any files are created when hashed files are pre-loaded - perhaps somebody else could comment.

If the /tmp directory gets full then problems will occur. Also, it might cause problems for other applications on the same server. I think that a separate file system for DataStage temp files is advisable, as it allows for more control, when sizing or purging.

After changing dsenv, remember to stop and start the services.


----- Original Message -----
From:
To:
Sent: Thursday, December 13, 2001 6:41 PM
Subject: Using /tmp directory


> Hi all,
>
> We are running DataStage 4.0 on Solaris box.
> DataStage is using /tmp directory as a default for memory-mapping
> hashed files, which is defined in dsenv file:
>
> DS_MMAPPATH=/tmp; export DS_MMAPPATH
> DS_MMAPSIZE=32; export DS_MMAPSIZE
> DS_MAXWRITEHEAPS=1; export DS_MAXWRITEHEAPS
>
> Is it actually a good idea to use /tmp directory? How much space is
usually
> required?
>
> Thank you,
> Leonid Frumker
>
>
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Post by admin »

Thank you!




"DataStage Developer" on 12/13/2001 02:19:47 PM

Please respond to

To:
cc:

Subject: Re: Using /tmp directory


I know that if you are writing a hashed file with write cache enabled then this will cause memory map files to be created in the directory specified. I am not sure if any files are created when hashed files are pre-loaded - perhaps somebody else could comment.

If the /tmp directory gets full then problems will occur. Also, it might cause problems for other applications on the same server. I think that a separate file system for DataStage temp files is advisable, as it allows for more control, when sizing or purging.

After changing dsenv, remember to stop and start the services.


----- Original Message -----
From:
To:
Sent: Thursday, December 13, 2001 6:41 PM
Subject: Using /tmp directory


> Hi all,
>
> We are running DataStage 4.0 on Solaris box.
> DataStage is using /tmp directory as a default for memory-mapping
> hashed files, which is defined in dsenv file:
>
> DS_MMAPPATH=/tmp; export DS_MMAPPATH
> DS_MMAPSIZE=32; export DS_MMAPSIZE
> DS_MAXWRITEHEAPS=1; export DS_MAXWRITEHEAPS
>
> Is it actually a good idea to use /tmp directory? How much space is
usually
> required?
>
> Thank you,
> Leonid Frumker
>
>
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Post by admin »

What about uvconfig file?

# UVTEMP - is the name of the directory
# where UniVerse will put select lists
# and other internal temporary work
# files. This should be a fully
# qualified name of no more than 112
# characters.
UVTEMP /tmp

If we decide to change DS_MMAPPATH from /tmp to something else, then will this require to change UVTEMP as well?

Thank you,
Leonid




"DataStage Developer" on 12/13/2001 02:19:47 PM

Please respond to

To:
cc:

Subject: Re: Using /tmp directory


I know that if you are writing a hashed file with write cache enabled then this will cause memory map files to be created in the directory specified. I am not sure if any files are created when hashed files are pre-loaded - perhaps somebody else could comment.

If the /tmp directory gets full then problems will occur. Also, it might cause problems for other applications on the same server. I think that a separate file system for DataStage temp files is advisable, as it allows for more control, when sizing or purging.

After changing dsenv, remember to stop and start the services.


----- Original Message -----
From:
To:
Sent: Thursday, December 13, 2001 6:41 PM
Subject: Using /tmp directory


> Hi all,
>
> We are running DataStage 4.0 on Solaris box.
> DataStage is using /tmp directory as a default for memory-mapping
> hashed files, which is defined in dsenv file:
>
> DS_MMAPPATH=/tmp; export DS_MMAPPATH
> DS_MMAPSIZE=32; export DS_MMAPSIZE
> DS_MAXWRITEHEAPS=1; export DS_MAXWRITEHEAPS
>
> Is it actually a good idea to use /tmp directory? How much space is
usually
> required?
>
> Thank you,
> Leonid Frumker
>
>
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Post by admin »

UVTEMP is for internal Universe commands work area.
This is different from where DataStage writes its
heap and hash memory map files. You only really need
to worry about UVTEMP if youre using the UV/ODBC
stage. Otherwise, changing the dsenv file only
requires a recycling of services.

Good luck!

--- lfrumke@sears.com wrote:
>
> What about uvconfig file?
>
> # UVTEMP - is the name of the directory
> # where UniVerse will put select lists
> # and other internal temporary work
> # files. This should be a fully
> # qualified name of no more than 112
> # characters.
> UVTEMP /tmp
>
> If we decide to change DS_MMAPPATH from /tmp to
> something else, then will
> this require to change UVTEMP as well?
>
> Thank you,
> Leonid
>
>
>
>
> "DataStage Developer"
> on 12/13/2001
> 02:19:47 PM
>
> Please respond to
>
> To:
> cc:
>
> Subject: Re: Using /tmp directory
>
>
> I know that if you are writing a hashed file with
> write cache enabled
> then
> this will cause memory map files to be created in
> the directory specified.
> I
> am not sure if any files are created when hashed
> files are pre-loaded -
> perhaps somebody else could comment.
>
> If the /tmp directory gets full then problems will
> occur. Also, it might
> cause problems for other applications on the same
> server. I think that a
> separate file system for DataStage temp files is
> advisable, as it allows
> for
> more control, when sizing or purging.
>
> After changing dsenv, remember to stop and start the services.
>
>
> ----- Original Message -----
> From:
> To:
> Sent: Thursday, December 13, 2001 6:41 PM
> Subject: Using /tmp directory
>
>
> > Hi all,
> >
> > We are running DataStage 4.0 on Solaris box.
> > DataStage is using /tmp directory as a default
> for memory-mapping hashed
> > files, which is defined in dsenv file:
> >
> > DS_MMAPPATH=/tmp; export DS_MMAPPATH
> > DS_MMAPSIZE=32; export DS_MMAPSIZE
> > DS_MAXWRITEHEAPS=1; export DS_MAXWRITEHEAPS
> >
> > Is it actually a good idea to use /tmp directory?
> How much space is
> usually
> > required?
> >
> > Thank you,
> > Leonid Frumker
> >
> >
>
>
>
>
>
>


__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Post by admin »

Thank you Kenneth.
We do use ODBC Informix stages a lot.

Leonid




Kenneth Bland on 12/14/2001 11:30:44 AM

Please respond to

To: datastage-users@oliver.com
cc:

Subject: Re: Using /tmp directory


UVTEMP is for internal Universe commands work area.
This is different from where DataStage writes its
heap and hash memory map files. You only really need
to worry about UVTEMP if youre using the UV/ODBC
stage. Otherwise, changing the dsenv file only
requires a recycling of services.

Good luck!

--- lfrumke@sears.com wrote:
>
> What about uvconfig file?
>
> # UVTEMP - is the name of the directory
> # where UniVerse will put select lists
> # and other internal temporary work
> # files. This should be a fully
> # qualified name of no more than 112
> # characters.
> UVTEMP /tmp
>
> If we decide to change DS_MMAPPATH from /tmp to
> something else, then will
> this require to change UVTEMP as well?
>
> Thank you,
> Leonid
>
>
>
>
> "DataStage Developer"
> on 12/13/2001
> 02:19:47 PM
>
> Please respond to
>
> To:
> cc:
>
> Subject: Re: Using /tmp directory
>
>
> I know that if you are writing a hashed file with
> write cache enabled
> then
> this will cause memory map files to be created in
> the directory specified.
> I
> am not sure if any files are created when hashed
> files are pre-loaded -
> perhaps somebody else could comment.
>
> If the /tmp directory gets full then problems will
> occur. Also, it might
> cause problems for other applications on the same
> server. I think that a
> separate file system for DataStage temp files is
> advisable, as it allows
> for
> more control, when sizing or purging.
>
> After changing dsenv, remember to stop and start the services.
>
>
> ----- Original Message -----
> From:
> To:
> Sent: Thursday, December 13, 2001 6:41 PM
> Subject: Using /tmp directory
>
>
> > Hi all,
> >
> > We are running DataStage 4.0 on Solaris box.
> > DataStage is using /tmp directory as a default
> for memory-mapping hashed
> > files, which is defined in dsenv file:
> >
> > DS_MMAPPATH=/tmp; export DS_MMAPPATH
> > DS_MMAPSIZE=32; export DS_MMAPSIZE
> > DS_MAXWRITEHEAPS=1; export DS_MAXWRITEHEAPS
> >
> > Is it actually a good idea to use /tmp directory?
> How much space is
> usually
> > required?
> >
> > Thank you,
> > Leonid Frumker
> >
> >
>
>
>
>
>
>


__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Post by admin »

If you do decide to change the uvconfig file then you will need to tell DataStage to start using the new configuration settings. This is done using the uvregen command located in the DataStage Server Engine bin directory. After making the change do the following :

cd `cat /.uvhome`
. ./dsenv
bin/uvregen

To check if the change has taken effect use:

bin/uvregen -t

this will list all the active uvconfig settings.

You might also need to stop and start DataStage services.

----- Original Message -----
From:
To:
Sent: Friday, December 14, 2001 3:58 PM
Subject: Re: Using /tmp directory


>
> What about uvconfig file?
>
> # UVTEMP - is the name of the directory
> # where UniVerse will put select lists
> # and other internal temporary work
> # files. This should be a fully
> # qualified name of no more than 112
> # characters.
> UVTEMP /tmp
>
> If we decide to change DS_MMAPPATH from /tmp to something else, then
> will this require to change UVTEMP as well?
>
> Thank you,
> Leonid
>
>
>
>
> "DataStage Developer" on 12/13/2001
> 02:19:47 PM
>
> Please respond to
>
> To:
> cc:
>
> Subject: Re: Using /tmp directory
>
>
> I know that if you are writing a hashed file with write cache
> enabled then this will cause memory map files to be created in the
> directory specified. I
> am not sure if any files are created when hashed files are pre-loaded -
> perhaps somebody else could comment.
>
> If the /tmp directory gets full then problems will occur. Also, it
> might cause problems for other applications on the same server. I
> think that a separate file system for DataStage temp files is
> advisable, as it allows for more control, when sizing or purging.
>
> After changing dsenv, remember to stop and start the services.
>
>
> ----- Original Message -----
> From:
> To:
> Sent: Thursday, December 13, 2001 6:41 PM
> Subject: Using /tmp directory
>
>
> > Hi all,
> >
> > We are running DataStage 4.0 on Solaris box.
> > DataStage is using /tmp directory as a default for memory-mapping
hashed
> > files, which is defined in dsenv file:
> >
> > DS_MMAPPATH=/tmp; export DS_MMAPPATH
> > DS_MMAPSIZE=32; export DS_MMAPSIZE
> > DS_MAXWRITEHEAPS=1; export DS_MAXWRITEHEAPS
> >
> > Is it actually a good idea to use /tmp directory? How much space is
> usually
> > required?
> >
> > Thank you,
> > Leonid Frumker
> >
> >
>
>
>
>
>
>
>
Locked