Checking a record number

If the URL :

http://vso2.tuc.noao.edu/cgi-bin/drms_test/drms_export.cgi?series=hmi__M_45s;record=12697191-12697191

fails to download, then we need to use show_info to check on that record number and get a storage unit number (sunum) :

show_info -S ds="hmi.m_45s[?t_rec_index=12697191?]"
sunum
136331652

And then query JSOC about that sunum :

wget -O - "http://jsoc.stanford.edu/cgi-bin/ajax/jsoc_fetch_VSO?op=exp_su&method=url_quick&requestid=none&formatvar=dataobj&format=json&protocol=as-is&sunum=136331652"

which might return something like :

{"count":1,"size":0,"dir":"","data":{"136331652":{"sunum":"136331652","series":"NA","path":"NA","sustatus":"N","susize":"0"}},"requestid":"","method":"url_quick","protocol":"as-is","wait":0,"status":0}

Indicating that the sunum does not exist at JSOC (the NA's indicating that things like the path are not properly set). It could be that this means that you have to contact JSOC to resolve the problem. Even after the problem is resolved, it could be that the local JMD has (correctly) marked it as being offline and won't download it until the JMD's internal database is cleaned out by doing something like :

/opt/JMD/bin/jmdij
delete from drms.su_cache where state='OFLN';
exit;

Or, equivalently :

echo "delete from drms.su_cache where state='OFLN';" | /opt/JMD/bin/jmdij

The path /opt/JMD may be different on your system depending on where the JMD is installed.