ESM1.6: Investigate behaviour when `jobnum=1`

[blimlim]

So far we've been using jobnum > 1 and runtype="continue". The access driver initialises the model differently, when jobnum=1:

cice5/drivers/access/CICE_InitMod.F90

Lines 159 to 164 in 0bd0131

	idate_save = idate !save for late re-set in case 'restart' is used for jobnum=1
	!and mess up the calendar idate for this exp...!
	if (jobnum==1) then
	nrec = month - 1 !month is from calendar
	if (nrec == 0) nrec = 12
	call get_time0_sstsss(trim(inputdir)//'/monthly_sstsss.nc', nrec)

cice5/drivers/access/CICE_InitMod.F90

Lines 189 to 194 in 0bd0131

	if (jobnum == 1 ) then
	time = 0.0 !NOTE, the first job must be set back to 0 and
	idate = idate_save !idate back to the 'initial' value, in any case
	else !BX: 20160720
	time = runtime0 !............
	endif

The restart/initialisation method when jobnum=1 is not very clear, and as noted here the runtype setting can be changed independently of jobnum. It would good to investigate how the code is behaving, and whether problems can occur from inconsistent runtype, jobnum and calendar settings.