Goodbye ‘RP’, hello ‘PH’ (or ‘PHL’)!

Did you know that the Philippine Department of Foreign affairs recently decided to adopt PH (or PHL) as the official acronym of the Republic of the Philippines, instead of the ‘RP’ moniker?

The DFA Secretary issued an order last October 20 directing all Philippine embassies and consulate offices around the world to drop the ‘RP’ tag and use ‘PH’, or ‘PHL’, instead.

This directive finally makes us ‘standards compliant’ with regards to the country code standard defined by the International Organization for Standardization, or ISO.

This is a welcome change although it might take a while for most people to get used to. (In sports, try to imagine cheering for our Filipino athletes/contingent while shouting “Go Team PH!” or “Go PH Team!”, instead of the usual “Go RP Team!”)

But…. come to think of it, on a broader scale, you’ll probably notice that the ‘RP’ tag isn’t used much anyway — particularly in the internet. If you take a look at social media sites such as Facebook and Twitter — or even in daily email correspondence — people actually do tend to use ‘PH’ more. You’ll see “PH-time”, “PHP”, and in its most obvious form — in internet domain names, where we use .ph, instead of .rp as a top level domain name.

Reference Sites:
GMANews.tv: Philippine diplomats will now use PH or PHL instead of RP
Philstar.com: DFA junks ‘RP’ for ‘PH’ or ‘PHL’

How to call a batch file from within another batch file

Have you tried running an external batch file from within a batch file or script, only to find out that the original batch file script terminated as soon as the external batch script is executed?

For example:

Let’s say we have a main script called “mainscript.bat” and two external scripts called “external1.bat” and “external2.bat”, with “mainscript.bat” having the following lines:

@echo off
c:testscriptsexternal1.bat
c:testscriptsexternal2.bat

When you try to run the script, you’ll notice that external1.bat will run but external2.bat won’t. This is because external1.bat (the called script) won’t pass the control back to mainscript.bat (the calling script) — which means it won’t get to run external2.bat.

In order to pass the control back to the calling script, you need to use the “CALL” command.

Here’s a simple fix for mainscript.bat:

@echo off
CALL c:testscriptsexternal1.bat
CALL c:testscriptsexternal2.bat

When you run mainscript.bat,  it will call (run) external1.bat. When external1.bat finishes, it will pass the control back to mainscript.bat. Which will then process the next line on the script — in this case, it will call (run) external2.bat — and so on.