Personal tools
You are here: Home User Support User Documentation FAQ 2 General DEISA FAQ

2 General DEISA FAQ

Q: How do I access my Execution Site using the DEISA network or my personal laptop?

The answer may be found at the following link: Alternatively, you may ask your Home Site for assistance.

Q: How can I determine the status of each component of the DEISA infrastructure?

You can view the status of each component of the DEISA infrastructure via the INCA monitoring service at

Q: I have connection problems (ssh-keys, machine not available, maintenance problems, etc.)

You can have a look at the INCA tool ( to see if the site is in maintenance or has problems with the service you are trying to use. Additionally the website of your Execution Site may have further information. If INCA does not provide an answer, please submit a query to the DEISA Trouble Ticket System (DTTS), at For more information on the DTTS, please visit

Q: How do I submit a query for support?

Rather than submitting queries to an individual DEISA site, we strongly recommend using the DEISA Trouble Ticket System. For more details, please visit

Q: May I contact my Execution Site directly?

Please do not contact your Execution Site directly. Instead, please communicate via the DEISA Trouble Ticket System (DTTS). For more details, please visit

Q: Why do I get “command not found” errors for almost every command?

The most probable reason is that you don’t have the DEISA Common Production Environment (DCPE) loaded. In order to load the DCPE, type:

module load deisa

Indeed, every new shell must start with this command, i.e. it must be the first executable line in any batch script and the first command typed when you first log in.

Q: How can I check how many hours I have consumed?

You can check how many hours you have consumed using the DEISA Accounting Reporting Tool (DART). 

For more information and for the DART FAQ, please visit

To launch the tool directly, please click here:

NB Some DEISA sites do report usage figures using their own tools elsewhere; however, the only official source of DEISA accounting data is given by the DART.

Q: I have platform-specific questions and problems: where can I find local documentation?

There is a link to each sites’ local User Documentation via DEISA’s Interactive Access User Document at

Q: How do I submit a job?

This is described in DEISA’s Batch System User Document, which is available via

Q: What is the deisa_service script?

Users do not need to know a particular address and/or port number when using a Globus command directly on the command-line of a DEISA machine, as DEISA has provided the deisa_service script.  To access the deisa_service script, you must first load both the deisa and globus modules. The deisa_service script provides abbreviations for the user to employ, which encode addresses and port numbers.  These abbreviations make Globus commands shorter, easier to read/write, and more robust as changes to any particular Globus address or port details need not be known by the user.  For example, the command

gsissh `deisa_service -e -s lrz`

provides a shorthand for the full command of

gsissh -p 2222

Note, too, that users can specify if they wish to employ the DEISA network (-i for internal) or the public Internet (-e for external).  The –s flag informs the deisa_service that gsissh is being employed.  If you call deisa_service without any parameters, you will get a help screen explaining all possibilities and listing example calls for deisa_service with frequently used Globus commands. NB to employ the deisa_service, users must first run the following command.

module load deisa

Q: How do I increase my file space or the limit on the total number of files?

Please contact your Home Site who will then investigate the possibility of increasing your disc allocation at your Execution Site(s).

Q: Which non-DEISA tools are available on my Execution Site?

There is a link to each sites’ local User Documentation via DEISA’s Interactive Access User Document at, where such tools will be described.

Q: How to convert binary files from little endian to big endian and visa-versa on an IBM BlueGene platform?

You can use the environment variable XLFRTEOPTS; however this does not work with files generated via MPI-IO. If you want to read or write a file in LittleEndian on unit 12 of an IBM BlueGene:

BlueGene>mpixlf90_r -o little_endian little_endian.f90
BlueGene>bgrun -np 64 -mode VN -env "XLFRTEOPTS=ufmt_littleendian=12" -exe little_endian

Q: At the end of the project, how long do I have access to my data?

Typically, each project is given up to 3 months to remove their data from their Execution Site(s), however this should be confirmed with your Home Site.

Q: At the end of the project, how do I transfer my data to a remote computer?

If you have access to the $DEISA_DATA common file-system at both your Home Site and Execution Site, you can transfer your files into that space and access it from your Home Site. NB $DEISA_DATA is not backed up. If you have no access to $DEISA_DATA at one of your sites, then you will have to use GridFTP or scp.  We strongly recommend using GridFTP due to its much greater performance for larger file transfers.  See for details.

Q: My registration information has changed (this may be your name, address,
affiliation, e-mail, telephone number, etc). Should I tell DEISA?

Please inform DEISA via

Q: How should I acknowledge DEISA?

If you publish results which are derived from work performed using DEISA resources, then please reference DEISA in the following manner: ‘We thank the DEISA Consortium (, funded through the EU FP7 project RI-222919, for support within the DEISA Extreme Computing Initiative/DEISA Virtual Community Programme*’  (* delete as applicable). Finally, please inform DEISA so that we may include a reference to your publication in our website.

Document Actions