modified: JGLOBAL_FORECAST

A test showed that jobid is not defined in JGLOBAL_FORECAST running in the Rocoto environment.
jobid is defined in ./env files. Defining DATA without sourcing ./env/$nachine.env caused the
script to fail.  Move the definitin of DATA after sourcing env parameters

jobs/JGLOBAL_FORECAST

@@ -5,15 +5,6 @@ export RUN_ENVIR=${RUN_ENVIR:-"nco"}
 export PS4='$SECONDS + '
 date
 
-##############################################
-# Obtain unique process id (pid) and make temp directory
-##############################################
-export pid=${pid:-$$}
-export outid=${outid:-"LL$job"}
-export DATA=${DATA:-${DATAROOT}/${jobid:?}}
-mkdir -p $DATA
-cd $DATA
-
 
 ##############################################
 # Run setpdy and initialize PDY variables
@@ -72,6 +63,16 @@ status=$?
 [[ $status -ne 0 ]] && exit $status
 
 
+##############################################
+# Obtain unique process id (pid) and make temp directory
+##############################################
+export pid=${pid:-$$}
+export outid=${outid:-"LL$job"}
+export DATA=${DATA:-${DATAROOT}/${jobid:?}}
+mkdir -p $DATA
+cd $DATA
+
+
 # Set wave variables
 if [ ${DO_WAVE:-"NO"} = "YES" ]; then
   # WAVE component directory