# WARNING in subroutine OPEN3 **URL:** \ **Category:** CMAQ\ **Tags:** cmaq\ **Created:** [January 7, 2023, 7:45am UTC](https://forum.cmascenter.org/t/warning-in-subroutine-open3/3830 "2023-01-07T07:45:16Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![lifenx](https://avatars.discourse-cdn.com/v4/letter/l/c0e974/32.png) [@lifenx](https://forum.cmascenter.org/u/lifenx)\ **Post date:** [January 7, 2023, 7:45am UTC](https://forum.cmascenter.org/t/warning-in-subroutine-open3/3830/1 "2023-01-07T07:45:16Z")
Hi, I am having the following problem while running CMAQ5.3.2. My mechanic is cb6r3\_ae7\_aq, and MCIP5.0 for weather. Is this because my weather file failed to transfer? What should I do about it? ![image](https://canada1.discourse-cdn.com/flex027/uploads/cmas/original/2X/a/a1d91e96d1c6afed7e6165fc6185f4c6adc4a04a.png) ---
**Author:** ![cjcoats](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@cjcoats](https://forum.cmascenter.org/u/cjcoats)\ **Post date:** [January 7, 2023, 1:58pm UTC](https://forum.cmascenter.org/t/warning-in-subroutine-open3/3830/2 "2023-01-07T13:58:15Z")
You’re not giving us enough of the log to help diagnose the problem. Immediately before this `WARNING` will have been a message of the form > `MET_CRO_3D: *path-name for file*` and then the question is what the command _ls -l_ says about that physical path-name: is the file there, and if so, what are the permissions? ---
**Author:** ![lifenx](https://avatars.discourse-cdn.com/v4/letter/l/c0e974/32.png) [@lifenx](https://forum.cmascenter.org/u/lifenx)\ **Post date:** [January 7, 2023, 3:19pm UTC](https://forum.cmascenter.org/t/warning-in-subroutine-open3/3830/3 "2023-01-07T15:19:37Z")
Hi, I attach my log file, thank you for your help. Is it because my met file did not transfer successfully? ![image](https://canada1.discourse-cdn.com/flex027/uploads/cmas/original/2X/8/808f0ef0c033b8b8ce706cb9d197ee4659872a68.png) ---
**Author:** ![cjcoats](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@cjcoats](https://forum.cmascenter.org/u/cjcoats)\ **Post date:** [January 7, 2023, 3:23pm UTC](https://forum.cmascenter.org/t/warning-in-subroutine-open3/3830/4 "2023-01-07T15:23:52Z")
I repeat the above: what does the command _ls -l_ say about this file? (…and I’m not going to copy that entire path beginning with `/mnt` where you used an un-cut-and-paste-able image to display the log, instead of useful (either in-line cut-and-paste or attached-file) text…) ---
**Author:** ![lifenx](https://avatars.discourse-cdn.com/v4/letter/l/c0e974/32.png) [@lifenx](https://forum.cmascenter.org/u/lifenx)\ **Post date:** [January 10, 2023, 8:08am UTC](https://forum.cmascenter.org/t/warning-in-subroutine-open3/3830/5 "2023-01-10T08:08:16Z")
Sorry for replying you so long. I tried to change the compiler to pgi, but there was a new problem.I attach my run script and log file. [CTM\_LOG\_019.v532\_pgi\_cn36\_20190110.txt](https://forum.cmascenter.org/uploads/short-url/t3asCtF4pMe1cBhUhuFC1Rea9zW.txt) (8.9 KB) [run\_cctm\_pfas.txt](https://forum.cmascenter.org/uploads/short-url/ecH0jCZMWaQW6Ejo9MbHqcH6YiJ.txt) (36.7 KB) ---
**Author:** ![hogrefe.christian](https://avatars.discourse-cdn.com/v4/letter/h/74df32/32.png) [@hogrefe.christian](https://forum.cmascenter.org/u/hogrefe.christian)\ **Post date:** [January 10, 2023, 11:58am UTC](https://forum.cmascenter.org/t/warning-in-subroutine-open3/3830/6 "2023-01-10T11:58:48Z")
The error points to a different file, but the same problem, so the advice given by @cjcoats still stands. What does `ls -l /mnt/Data1/lifenx/test/inp/36km/icon/CCTM_v532_cn36_profile_2019010` say? (thanks for posting the run log as text file this time) ---
**Author:** ![lifenx](https://avatars.discourse-cdn.com/v4/letter/l/c0e974/32.png) [@lifenx](https://forum.cmascenter.org/u/lifenx)\ **Post date:** [January 11, 2023, 7:29am UTC](https://forum.cmascenter.org/t/warning-in-subroutine-open3/3830/7 "2023-01-11T07:29:25Z")
Hi，Thank you for your reply. This file is to store some variable information, I attach this file. [ICON\_v532\_cn36\_profile\_2019010.txt](https://forum.cmascenter.org/uploads/short-url/52b7W5CrDzrNuRjT49xfoggDWcu.txt) (72.4 KB) ---
**Author:** ![lifenx](https://avatars.discourse-cdn.com/v4/letter/l/c0e974/32.png) [@lifenx](https://forum.cmascenter.org/u/lifenx)\ **Post date:** [January 11, 2023, 7:42am UTC](https://forum.cmascenter.org/t/warning-in-subroutine-open3/3830/8 "2023-01-11T07:42:20Z")
I’m sorry for not giving you useful information before. I attach part of the met file. [METCRO3D\_cn36\_2019010.txt](https://forum.cmascenter.org/uploads/short-url/l885bEB1CKG1MdSG2IxJDJGr8Yo.txt) (46.2 KB) ---
**Author:** ![hogrefe.christian](https://avatars.discourse-cdn.com/v4/letter/h/74df32/32.png) [@hogrefe.christian](https://forum.cmascenter.org/u/hogrefe.christian)\ **Post date:** [January 11, 2023, 12:25pm UTC](https://forum.cmascenter.org/t/warning-in-subroutine-open3/3830/9 "2023-01-11T12:25:27Z")
Thanks for posting these files. However, the error message is more fundamental, it does not point to a problem with the _ **contents** _ of the file, but to a problem with even being able to _ **access** _ it. Put differently, the executable cannot find the file at the location specified in the run script, which points to a problem with path and/or file name definitions in the run script. The log file tells you exactly where the executable is looking for the input file when it fails, so just running the `ls -l` system command with the relevant full file name and path from the log file as argument as mentioned by @cjcoats in posts 2 and 4 should confirm that there was an error with the path, and you can then proceed with fixing the path and/or filename specified in the run script. In your third post, you mention that you got past the error for opening MET\_CRO\_3D, and you also mention changing the compiler. Changing the compiler should not have affected this particular error, so I’m guessing you also made a change to the run script to fix the path and/or file name of the MET\_CRO\_3D file. If that’s the case, now you need to do the same for the ICON file. Actually, looking at your attachments again now, I think you’re setting the file name for ICFILE incorrectly. Your setting is `setenv ICFILE CCTM_v532_cn36_profile_2019010` which matches what the program is looking for in the error message you posted (/mnt/Data1/lifenx/test/inp/36km/icon/CCTM\_v532\_cn36\_profile\_2019010), but the header you shared in your last post suggests that the file is actually named ICON\_v532\_cn36\_profile\_2019010 (which would be a more typical name for an initial condition name). So, the solution likely is to change `setenv ICFILE CCTM_v532_cn36_profile_2019010` to `setenv ICFILE ICON_v532_cn36_profile_2019010` in your run script, and of course also double check the setting of ICPath to make sure that that’s where the file resides. ---
**Author:** ![lifenx](https://avatars.discourse-cdn.com/v4/letter/l/c0e974/32.png) [@lifenx](https://forum.cmascenter.org/u/lifenx)\ **Post date:** [January 11, 2023, 2:25pm UTC](https://forum.cmascenter.org/t/warning-in-subroutine-open3/3830/10 "2023-01-11T14:25:41Z")
Thank you for your advice. I have realized this problem. I will check the path of my file.