Australian Bureau of Statistics

Rate the ABS website
ABS Home > Statistics > By Catalogue Number
ABS @ Facebook ABS @ Twitter ABS RSS ABS Email notification service
1406.0.55.002 - User Manual: ABS Remote Access Data Laboratory (RADL), Mar 2006  
Latest ISSUE Released at 11:30 AM (CANBERRA TIME) 22/02/2012  Reissue
   Page tools: Print Print Page Print all pages in this productPrint All RSS Feed RSS Bookmark and Share Search this Product  
Contents >> Frequently asked questions >> Errors and problems

ERRORS AND PROBLEMS

Why can't I see my approved CURFs in the RADL?
I get an error message saying that the dataset can't be found
I get an error message saying that the variable can't be found
What do I do if a job does not appear to be progressing?
What do I do if I am having coding problems?
My output is being denied but I'm not sure why
Why can't I use bootstrapping commands in RADL?
What are Parser Errors?

Why can't I see my approved CURFs in the RADL?
There are three possible reasons:

  • Check that you have completed all steps in the Submit new request screen. For further assistance see the Submitting a request in the RADL section of the User Manual: ABS Remote Access Data Laboratory (RADL).
  • For some CURFs, additional RADL user IDs are allocated to approved users. Some users will have user identifiers ending with "_INNOV", "_STATE", "_DETAIL", or "_REM". If you have one of these user IDs you should log in with each of your user IDs to check whether the CURF you want to use is attached to your other ID.
  • Your application for access may not have been finalised yet . Check in MiCRO to see the status of your CURF application or contact microdata.access@abs.gov.au or call 02 6252 7714 for assistance.
I get an error message saying that the dataset can't be found
Check that the dataset is being referenced correctly. Information on library and dataset names is available in the 'CURF reference documentation' link in the navigator of the RADL.

If you are trying to access a saved dataset, check that the dataset exists. You can do this by using File management command code.

I get an error message saying that the variable can't be found
Check that the variable is being spelt correctly (especially check for underscores, and the case) and that the variable is available on the CURF being accessed. Information on variable names is available in the 'CURF reference documentation' link in the navigator of the RADL. A common problem is that a variable may be available one level of the CURF but not another, for example on the household level file, but not the person level file.

What do I do if a job does not appear to be progressing?
If a normal job (not including long jobs) does not appear to be progressing after 10 minutes and has a status of 'submitted', you can:
  • check your log file and code for mistakes
  • check that you have retained all unit identifiers
  • check for RADL alerts - occasionally ABS conduct routine maintenance that may affect RADL users
  • try submitting your job again.
If the job still doesn't complete, contact the RADL Administrator for assistance by emailing radl@abs.gov.au or call 02 6252 7714.

What do I do if I am having coding problems?
The ABS does not provide a code advisory service however the ABS have produced introductory RADL tutorials for SAS, SPSS or Stata. The tutorials introduce users to the RADL system and use code to produce basic tables and statistics. The tutorials are available in the 'Information for all RADL Users' link in the navigator of the RADL.

Here are some common problems that users experience:
  • failing to reference the CURF properly
  • not typing variable names in upper case when using Stata.
Common problems with SAS code:
  • missing, or extra semicolons - check that your semicolons are where they should be
  • missing 'by' statements when merging data sets
  • merging levels within a CURF with variables that exist on both, but don't always take the same value on both
  • performing character operations with numeric variables, or vice versa
  • attempting to use banned commands.
Common problems with Stata code:
  • attempting to use user-written packages which have not been added to the RADL
  • attempting to use banned commands (particularly svrtab)
  • excessively long lines of code (use continuation character "///" and start a new line).
Check your job's log file to see where the errors are occurring within your code, this will help determine where your code is going wrong.

My output is being denied but I'm not sure why
Output may be denied due to exceeding file size or level of detail limits. You can try splitting your code or output into smaller sections. While this is allowed for aggregate output, note that cumulatively downloaded unit record level output is not allowed and is audited.

RADL SPSS sometimes denies output and does not print an appropriate error message as a result of code references to non-existent variables. Check the spelling of all variables (especially underscores) and re-run your job. For further information about variable names, see the data item list in the 'CURF reference documentation' link in the navigator of the RADL.

Why can't I use bootstrapping commands in RADL?
Bootstrapping commands are banned in RADL.

To use bootstrap commands appropriately a user needs to be able to identify the Primary Selection Units (PSU). In the case of ABS CURFs, all respondents in the same Collection District (CD) belong to the same PSU. However, grouping respondents into PSUs significantly increases the risk of a respondent being identified so the ABS cannot release this information. To enable researchers to produce accurate variance estimates, the ABS releases the replicate weights which take the sample design into consideration, as well as any other steps in the estimation process such as non-response adjustments.

For Stata users, the ABS has made available the user-supplied svr suite of commands to assist users in calculating standard errors using replicate weights. See the How can I use the replicate weights in analysis or estimation of sampling error? section of the Survey and replicate weights section of the User Manual: ABS Remote Access Data Laboratory (RADL).

What are Parser Errors?
Parser errors occur when a conflict arises between a user's code and the built-in protections of the RADL and usually occurs in conjunction with the use of 'Array' statements. To fix a parser error you will need to alter the code. Additionally the following words are considered 'keywords' in SAS and can't be used as variable names in the RADL.
AND
BETWEEN
CALL
CARDS
CARDS4
CONTAINS
DATA
DATALINES
DATALINES4
DO
ELSE
END
EQ
FILE
GE
GT
IF
IN
IS
LAST
LE
LIKE
LINES
LINES4
LOG
LT
MAX
MERGE
MIN
MISSING
MODIFY
NE
NOT
NULL
OPTIONS
OR
OTHERWISE
OUT
PROC
QUIT
SAME
SELECT
SET
SQL
TABLES
THEN
TITLE
UPDATE
WHEN


Previous PageNext Page

Bookmark and Share. Opens in a new window


Commonwealth of Australia 2014

Unless otherwise noted, content on this website is licensed under a Creative Commons Attribution 2.5 Australia Licence together with any terms, conditions and exclusions as set out in the website Copyright notice. For permission to do anything beyond the scope of this licence and copyright terms contact us.