126.96.36.199 Creating An Executable ISCST.
The ISCST model can be compiled and linked in one step under VS FORTRAN by executing the appropriate procedure (e.g., VSF2CG to compile and load) in the JCL for the compile job. It is easiest to concatenate all of the source (*.FOR) files into a single partitioned data set member, and identify that file name with a DD statement in the JCL. Special procedures may be needed to access the INCLUDE files, where each INCLUDE file should be a member in a partitioned data set.
188.8.131.52 Running ISCST.
When running the ISCST model under IBM/MVS, special attention is needed to defining and controlling the file I/O. The input runstream file is read from the default input unit, Fortran unit number 5, and the output print file is written to the default output unit, Fortran unit number 6. The input meteorological data file is read from Fortran unit 19. Other system files include the temporary error/message file (unit 10) and the temporary event file for ISCST (unit 18). These files, as well as any user‑specified optional output files, must be defined with DD statements in the JCL.
4.3.4 Various UNIX machines (CRAY, SUN, DEC VAX, AT&T)
184.108.40.206 Compiler/System Dependent Preprocessing.
The ISC codes as provided on the SCRAM BBS are compatible with any ANSI Standard FORTRAN 77 Compiler operating under UNICOS, UNIX, and SUN OS, except that the PC‑specific features contained in PCCODE.FOR must be replaced with equivalent system-specific functions for UNIX (which may be called UNIXCODE.FOR), or commented out. These features include writing the date and time on each page of the printed output file and writing an update to the screen on the status of processing.
220.127.116.11 Creating An Executable ISCST.
Although the users can specify any way they want to group and store the code and data files, the easiest way is to copy all the source codes modules, INCLUDE files and meteorology data into a subdirectory. The users should make sure that every source file has suffix .f and the file name should be a lower case ASCII character string, because the UNICOS, UNIX, and SUN OS is case‑sensitive. Also, for the same reason, all of the .INC file should be in UPPER CASE. The user can then write a make file to compile, link and create an executable.
The files needed to make the ISCST executable are the following:
MAIN1.INC, MAIN2.INC, MAIN3.INC, DEPVAR.INC, iscst3.f, (unixcode.f), setup.f, coset.f, soset.f, reset.f, meset.f, tgset.f, ouset.f, inpsum.f, metext.f, calc1.f, calc2.f, prise.f, sigmas.f, calc3.f, calc4.f, depflux.f, pitarea.f, output.f
251 - 252 - 253 - 254 - 255 - 256 - 257 - 258 - 259 - 260 - 261 - 262 - 263 - 264 - 265 - 266 - 267 - 268 - 269 - 270 - 271 - 272 - 273 - 274 - 275 - 276 - 277 - 278 - 279 - 280 - 281 - 282 - 283 - 284 - 285 - 286 - 287 - 288 - 289 - 290 - 291 - 292 - 293 - 294 - 295 - 296 - 297 - 298 - 299 - 300
deutsch: DIS CUS DES RAD
castellano: DIS CUS DES RAD english: DIS CUS DES RAD
português: DIS CUS DES RAD italiano: DIS CUS DES RAD
français: DIS CUS DES RAD